Module: kamailio
Branch: 5.8
Commit: 6533c42fc0bba6408376a8f8b41b02b97b04ca1b
URL: https://github.com/kamailio/kamailio/commit/6533c42fc0bba6408376a8f8b41b02b…
Author: Xenofon Karamanos <22965395+xkaraman(a)users.noreply.github.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-03-07T10:06:56+01:00
tls/docs: Update tls.reload docs
(cherry picked from commit 4c9cfa7a6a770a693ecb3b840ad042fb201db675)
---
Modified: src/modules/tls/doc/rpc.xml
Modified: src/modules/tls/doc/tls.xml
---
Diff: https://github.com/kamailio/kamailio/commit/6533c42fc0bba6408376a8f8b41b02b…
Patch: https://github.com/kamailio/kamailio/commit/6533c42fc0bba6408376a8f8b41b02b…
---
diff --git a/src/modules/tls/doc/rpc.xml b/src/modules/tls/doc/rpc.xml
index 495fc7b31c2..d9e75b014b2 100644
--- a/src/modules/tls/doc/rpc.xml
+++ b/src/modules/tls/doc/rpc.xml
@@ -70,6 +70,10 @@
terminated and they continue to use the old certificates. The new configuration
will be used for new connections.
</para>
+ <para>
+ Reload is generally safe and usable in production environments. If possible should
+ be done in a time where the service has lower usage/connections.
+ </para>
<para>
This RPC command is exported with "RPC_EXEC_DELTA" flag, therefore its
execution rate can be restricted to specific time intervals by setting
diff --git a/src/modules/tls/doc/tls.xml b/src/modules/tls/doc/tls.xml
index 9460d73c89f..9b3f4eaacb3 100644
--- a/src/modules/tls/doc/tls.xml
+++ b/src/modules/tls/doc/tls.xml
@@ -284,10 +284,6 @@ make -C modules/tls extra_defs="-DTLS_WR_DEBUG -DTLS_RD_DEBUG"
but also not exactly standard conforming (the verification should happen during TLS
connection establishment and not after).
</para>
- <para>
- TLS specific config reloading is not safe, so for now better don't use it,
- especially under heavy traffic.
- </para>
<para>
This documentation is incomplete.
The provided selects are not documented in this file. A list with all the
@@ -364,4 +360,3 @@ event_route[tls:connection-out] {
</section>
</chapter>
</book>
-
Hello,
discussed a bit during the online Kamailio devel meeting, it is time to
set the milestones towards the next major Kamailio release series v5.8.x.
If no other suggestions that suit more developers, I would propose to
freeze by end of this month or early February, then test for about 4
weeks as usual and release by end of February or during March.
If anyone wants to add new features/modules, they have to be published
till freezing date, either pushed in the git repository or proposed as
pull request.
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, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.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 -->
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #3717
#### Description
<!-- Describe your changes in detail -->
This PR updates some of the TLS documentation.
tls.reload: See #3717 for details and suggestions from core developers.
certificate generation: According to the History section, certificates are no longer generated automatically. Instead, the command `make install-tls-cert` should be used. This was verified to be working as intended and added suggestion in `Quick Start` section.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3776
-- Commit Summary --
* tls/docs: Update tls.reload docs
* tls/docs: Update certificate generation docs
-- File Changes --
M src/modules/tls/doc/rpc.xml (4)
M src/modules/tls/doc/tls.xml (10)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3776.patchhttps://github.com/kamailio/kamailio/pull/3776.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3776
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3776(a)github.com>
Module: kamailio
Branch: master
Commit: 67785fea8f906236e4a30bc09bb11b3292c46572
URL: https://github.com/kamailio/kamailio/commit/67785fea8f906236e4a30bc09bb11b3…
Author: Xenofon Karamanos <22965395+xkaraman(a)users.noreply.github.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-03-06T19:40:26+01:00
tls/docs: Update certificate generation docs
---
Modified: src/modules/tls/doc/tls.xml
---
Diff: https://github.com/kamailio/kamailio/commit/67785fea8f906236e4a30bc09bb11b3…
Patch: https://github.com/kamailio/kamailio/commit/67785fea8f906236e4a30bc09bb11b3…
---
diff --git a/src/modules/tls/doc/tls.xml b/src/modules/tls/doc/tls.xml
index 9b3f4eaacb3..5697792655a 100644
--- a/src/modules/tls/doc/tls.xml
+++ b/src/modules/tls/doc/tls.xml
@@ -93,7 +93,10 @@
</para>
<para>
When installing tls module of kamailio, a sample 'tls.cfg' file is deployed in the same
- folder with 'kamailio.cfg', along with freshly generated self signed certificates.
+ folder with 'kamailio.cfg'. For freshly generated self signed certificates make must be called from tls folder
+ <programlisting>
+make install-tls-cert
+ </programlisting>
</para>
<para>
HINT: be sure you have <emphasis>enable_tls=yes</emphasis> to your kamailio.cfg.
Module: kamailio
Branch: master
Commit: 4c9cfa7a6a770a693ecb3b840ad042fb201db675
URL: https://github.com/kamailio/kamailio/commit/4c9cfa7a6a770a693ecb3b840ad042f…
Author: Xenofon Karamanos <22965395+xkaraman(a)users.noreply.github.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-03-06T19:40:26+01:00
tls/docs: Update tls.reload docs
---
Modified: src/modules/tls/doc/rpc.xml
Modified: src/modules/tls/doc/tls.xml
---
Diff: https://github.com/kamailio/kamailio/commit/4c9cfa7a6a770a693ecb3b840ad042f…
Patch: https://github.com/kamailio/kamailio/commit/4c9cfa7a6a770a693ecb3b840ad042f…
---
diff --git a/src/modules/tls/doc/rpc.xml b/src/modules/tls/doc/rpc.xml
index 495fc7b31c2..d9e75b014b2 100644
--- a/src/modules/tls/doc/rpc.xml
+++ b/src/modules/tls/doc/rpc.xml
@@ -70,6 +70,10 @@
terminated and they continue to use the old certificates. The new configuration
will be used for new connections.
</para>
+ <para>
+ Reload is generally safe and usable in production environments. If possible should
+ be done in a time where the service has lower usage/connections.
+ </para>
<para>
This RPC command is exported with "RPC_EXEC_DELTA" flag, therefore its
execution rate can be restricted to specific time intervals by setting
diff --git a/src/modules/tls/doc/tls.xml b/src/modules/tls/doc/tls.xml
index 9460d73c89f..9b3f4eaacb3 100644
--- a/src/modules/tls/doc/tls.xml
+++ b/src/modules/tls/doc/tls.xml
@@ -284,10 +284,6 @@ make -C modules/tls extra_defs="-DTLS_WR_DEBUG -DTLS_RD_DEBUG"
but also not exactly standard conforming (the verification should happen during TLS
connection establishment and not after).
</para>
- <para>
- TLS specific config reloading is not safe, so for now better don't use it,
- especially under heavy traffic.
- </para>
<para>
This documentation is incomplete.
The provided selects are not documented in this file. A list with all the
@@ -364,4 +360,3 @@ event_route[tls:connection-out] {
</section>
</chapter>
</book>
-
Hi
When I add a destination to MySQL server to block and use kamcmd to reload, the call will not be blocked, while if I use kamcmd to add destination with `secfilter.add_dst` it works properly. It's considerable that after reloading if I print the blocked list in kamcmd (with `secfilter.print`) new database row will be printed correctly.
my secfilter SQL table:
+----+--------+------+------+
| id | action | type | data |
+----+--------+------+------+
| 1 | 2 | 4 | 1111 |
+----+--------+------+------+
kamailio 5.4.6 (x86_64/linux)
Ubuntu 22.04.3 LTS
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3694
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3694(a)github.com>
The uac module lacks the uac_reg_unregister(attr, val) method, Send REGISTER with expires 0 for matching record in real time, instead of through RPC command。uac_reg_disable(attr, val) :SIP processing is done on the next timer routine.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3702
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3702(a)github.com>