<!-- 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 - [ ] Small bug fix (non-breaking change which fixes an issue) - [X] 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 --> - [ ] PR should be backported to stable branches - [X] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description This PR restores the default behaviour of stable branch and makes libssl thread-guard work opt-in. - user's config from 5.7.3 will run unchanged - backport tls_threads_mode = 0|1|2 from dev; user must explicitly opt-in to libssl changes Scenario 1: user does not change 5.7.3 configuration; then libssl thread-guards will be disabled and Kamailio will run as before Scenario 2: user must opt-in to libssl thread-guards; `tls_threads_mode` has been backported from dev and user must use `tls_threads_mode = 1` in the configuration. The default value is `tls_threads_mode = 0` You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3754 -- Commit Summary -- * core: added tls_threads_mode global parameter * core/rthreads.h: use global ksr_tls_threads_mode to constrain thread * Sample etc/kamailio.cfg: global var tls_threads_mode * tls: restore default to bypass thread guards -- File Changes -- M etc/kamailio.cfg (17) M src/core/cfg.lex (2) M src/core/cfg.y (9) M src/core/globals.h (1) M src/core/rthreads.h (33) M src/main.c (5) M src/modules/tls/tls_mod.c (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3754.patch https://github.com/kamailio/kamailio/pull/3754.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3754 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3754(a)github.com>