Sorry for not being specific in [#1567](https://github.com/kamailio/kamailio/issues/1567). I had to clarify that I was talking about server role only.
>From what I understood server role configurations can be distinguish one from another only by socket, provided in their configuration. TLS module documentation says:
> "... different TLS parameters can be specified on a per role (server or client) and domain basis (for now only IPs)".
Which hints that additional tests for matching incoming connections against configured server profiles were in mind. I would like to request a feature which could allow matching them against domain name if that's possible.
One of the options may be checking client's certificate CN if _require_certificate_ parameter is set to yes.
Thank you!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1570
TLS module documentation says: "different TLS parameters can be specified on a per role (server or client) and domain basis (for now only IPs)". It would be nice feature if it could use same socket and distinguish connections by domain name.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1567
Apologies if i have not kept with the reporting standard.
Insertion attempts of out-of-credit replies from resume_on_initial_ccr callback, are corrupting the ro_session list. i.e. they nullify the first and last fields, which under certain conditions the first entry gets restored but not the last.This then crashes the process at ro_session_hash.c (link_ro_session), where the first entry has a valid address but the last does not.
Solution: ro_session_hash.h - unlink_unsafe_ro_session - check if the session to be linked is actually part of list i.e
if ((ro_session->next == 0x00) &&
(ro_session->prev == 0x00) &&
(ro_session != ro_session_entry->first) )
{
ro_session, &(ro_session->ro_tl),
ro_session->callid.len,
ro_session->callid.len,
ro_session->callid.s);
return;
}
rest of the code ....
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1549
impurecord.c: corrected small bug in remove_impucontact_from_list()
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [x] PR should be backported to stable branches
- [x] Tested changes locally against Version 5.1.0
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
corrected 2 small bugs in function remove_impucontact_from_list:
nullify tail->next if tail removed
in remove mid-list the pointer to previous contact was not set correctly
These issues were brought up by https://github.com/thulasizwe-n at another pull request:
https://github.com/kamailio/kamailio/pull/1547#issuecomment-395767031
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1562
-- Commit Summary --
* ims_usrloc_scscf:bugfix erraneous unlinking of deleted contact
-- File Changes --
M src/modules/ims_usrloc_scscf/impurecord.c (3)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1562.patchhttps://github.com/kamailio/kamailio/pull/1562.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1562