Sure, I can also output the "number" version, will add another commit. About the FIPS, other projects do it in a similar way (e.g. haproxy). But one simple change would be to have LM_INFO if FIPS is in fact enabled (this is rarely done), and DBG for FIPS mode not enabled, without the need for a new module parameter. Will change it.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/04208090638a639cdf03fafb1df161c…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/04208090638a639cdf03fafb1df161cd71f74c7e/146217533(a)github.com>
I would prefer to keep logging the OPENSSL_VERSION_NUMBER even for OPENSSL_VERSION_NUMBER >= 0x030000000L, it is something easy to extract by regex/grepping. In addition, the detailed version info can be printed.
I am not sure if FIPS logging is commonly used and relevant to be INFO, there will be questions when not enabled. IMO, DEBUG should do it here or a modparam (e.g., `libinfo`) can be introduced to dump exhaustive details about ssl library at startup (e.g., the version text, fips mode, ...).
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/04208090638a639cdf03fafb1df161c…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/04208090638a639cdf03fafb1df161cd71f74c7e/146217391(a)github.com>
I found and commited the mistake already before I saw the PR, then I amended the commit message to have it linked to it. I will split it in two lines then if required in the future, sure.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/228c59851878fed15d8b34e43938c28…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/228c59851878fed15d8b34e43938c281729e518d/146217108(a)github.com>
Credits and reference to issues or PRs have to be done in the description content of the commit message, not in the first line, as per contributing guidelines.
Also, as I could see if I haven't missed something, in this case the PR was proposing exactly the same change, with proper commit message, so it could have just been merged directly, not doing a separate commit and reference the PR.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/228c59851878fed15d8b34e43938c28…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/228c59851878fed15d8b34e43938c281729e518d/146216488(a)github.com>
<!-- 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 -->
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3966
-- Commit Summary --
* tls: Replace em dash with hyphen
-- File Changes --
M src/modules/tls/tls_mod.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3966.patchhttps://github.com/kamailio/kamailio/pull/3966.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3966
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3966(a)github.com>
Hello,
I am considering to release Kamailio v5.8.3 (out of branch 5.8) sometime
next week, most likely on Wednesday, Sep 4, 2024. If anyone is aware of
issues not yet on the bug tracker, report them there asap in order to
have a better chance to be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com