Hello,
I am considering to release Kamailio v6.0.1 (out of branch 60) on
Monday, March 10, 2025. 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
Kamailio Advanced Training, March 24-28, 2025 -- asipto.com
Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com
Added enable_register_publish parameter to enable REGISTER and PUBLISH method for topos
If set to 1 REGISTER and PUBLISH will be enabled for topos Currently only via header will be applied for topos and if mask_callid is set to 1 call-ID will be masked. Other headers should be manged by the user as required.
<!-- 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, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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)
- [ ] 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/3766
-- Commit Summary --
* add enable_register_publish
-- File Changes --
M src/modules/topos/topos_mod.c (2)
M src/modules/topos/tps_msg.c (132)
M src/modules/topos/tps_msg.h (2)
M src/modules/topos/tps_storage.c (6)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3766.patchhttps://github.com/kamailio/kamailio/pull/3766.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3766
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3766(a)github.com>
<!-- Kamailio Pull Request Template -->
Topos: Added get_callid_mask functin which will give the masked callID if actual callID is given and get_callid_unmask function which will unmask the given call-ID. This funtion is useful when the client sends a refer methord with refer-to header containing call-id
<!--
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
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3872
-- Commit Summary --
* add funtion to mask/unmask callID
* get_callid_mask /get_callid_unmask Document Update
-- File Changes --
M src/modules/topos/doc/topos_admin.xml (87)
M src/modules/topos/topos_mod.c (183)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3872.patchhttps://github.com/kamailio/kamailio/pull/3872.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3872
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3872(a)github.com>
Module: kamailio
Branch: master
Commit: 8b60b56015ced6da3666c6613e1189b9a1f63d8f
URL: https://github.com/kamailio/kamailio/commit/8b60b56015ced6da3666c6613e1189b…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2025-03-05T13:16:09+01:00
modules: readme files regenerated - auth ... [skip ci]
---
Modified: src/modules/auth/README
---
Diff: https://github.com/kamailio/kamailio/commit/8b60b56015ced6da3666c6613e1189b…
Patch: https://github.com/kamailio/kamailio/commit/8b60b56015ced6da3666c6613e1189b…
---
diff --git a/src/modules/auth/README b/src/modules/auth/README
index 193f91e0ef5..fcd73cc02a0 100644
--- a/src/modules/auth/README
+++ b/src/modules/auth/README
@@ -76,7 +76,7 @@ Daniel-Constantin Mierla
1.13. force_stateless_reply example
1.14. realm_prefix parameter example
1.15. force_stateless_reply example
- 1.16. use SHA-256 example
+ 1.16. algorithm example
1.17. add Authentication-Info header example
1.18. consume_credentials example
1.19. consume_credentials example
@@ -645,17 +645,18 @@ modparam("auth", "use_domain", 1)
3.18. algorithm (string)
Configure hash algorithm used for digest authentication. Possible
- values are "MD5" or "SHA-256". If left empty MD5 is used. If specified,
- the specified algorithm is used and is also put in the 'algorithm'
- field of the challenge header.
-
- Warning: SHA-256 hash values take twice the space of MD5 hash values.
- So a buffer overflow might occur if this option is used in combination
- with another auth_* module that does not allocate at least 65 bytes to
- store hash values. SHA-256 can safely be used with the module auth_db
- as it allocates 256 bytes to store HA1 values.
-
- Example 1.16. use SHA-256 example
+ values are "MD5", "SHA-256" or "SHA-512". If left empty MD5 is used. If
+ specified, the specified algorithm is used and is also put in the
+ 'algorithm' field of the challenge header.
+
+ Warning: SHA-256/512 hash values take twice or more the space of MD5
+ hash values. So a buffer overflow might occur if this option is used in
+ combination with another auth_* module that does not allocate at least
+ enough (65 or 129) bytes to store hash values. SHA-256/512 can safely
+ be used with the module auth_db as it allocates 256 bytes to store HA1
+ values.
+
+ Example 1.16. algorithm example
...
modparam("auth", "algorithm", "SHA-256")
...
Module: kamailio
Branch: master
Commit: 05c796ab406d5771d775769b380219c6bdcb67c1
URL: https://github.com/kamailio/kamailio/commit/05c796ab406d5771d775769b380219c…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2025-03-05T13:00:15+01:00
auth: docs updated for algorithm param
---
Modified: src/modules/auth/doc/auth_params.xml
---
Diff: https://github.com/kamailio/kamailio/commit/05c796ab406d5771d775769b380219c…
Patch: https://github.com/kamailio/kamailio/commit/05c796ab406d5771d775769b380219c…
---
diff --git a/src/modules/auth/doc/auth_params.xml b/src/modules/auth/doc/auth_params.xml
index 058c1d2706a..5e3f730bc39 100644
--- a/src/modules/auth/doc/auth_params.xml
+++ b/src/modules/auth/doc/auth_params.xml
@@ -705,20 +705,19 @@ modparam("auth", "use_domain", 1)
<title><varname>algorithm</varname> (string)</title>
<para>
Configure hash algorithm used for digest authentication.
- Possible values are "MD5" or "SHA-256". If left empty MD5 is used.
- If specified, the specified algorithm is used and is also put in
+ Possible values are "MD5", "SHA-256" or "SHA-512". If left empty MD5 is
+ used. If specified, the specified algorithm is used and is also put in
the 'algorithm' field of the challenge header.
</para>
<para>
- Warning: SHA-256 hash values take twice the space of MD5 hash values.
- So a buffer overflow might occur if this option is used in combination
- with another auth_* module that does not allocate at least 65 bytes to
- store hash values.
- SHA-256 can safely be used with the module auth_db as it allocates 256 bytes
- to store HA1 values.
+ Warning: SHA-256/512 hash values take twice or more the space of MD5 hash
+ values. So a buffer overflow might occur if this option is used in combination
+ with another auth_* module that does not allocate at least enough (65 or 129)
+ bytes to store hash values. SHA-256/512 can safely be used with the module
+ auth_db as it allocates 256 bytes to store HA1 values.
</para>
<example>
- <title>use SHA-256 example</title>
+ <title>algorithm example</title>
<programlisting>
...
modparam("auth", "algorithm", "SHA-256")