[sr-dev] git:5.8:ed99a5e2: modules: readme files regenerated - modules ... [skip ci]

Module: kamailio Branch: 5.8 Commit: ed99a5e2648c39e29fbbc7842c86425147c607c6 URL: https://github.com/kamailio/kamailio/commit/ed99a5e2648c39e29fbbc7842c86425… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2024-03-07T10:17:15+01:00 modules: readme files regenerated - modules ... [skip ci] --- Modified: src/modules/tls/README --- Diff: https://github.com/kamailio/kamailio/commit/ed99a5e2648c39e29fbbc7842c86425… Patch: https://github.com/kamailio/kamailio/commit/ed99a5e2648c39e29fbbc7842c86425… --- diff --git a/src/modules/tls/README b/src/modules/tls/README index 78af3bdcc77..d98f94eb8ed 100644 --- a/src/modules/tls/README +++ b/src/modules/tls/README @@ -263,8 +263,9 @@ Chapter 1. Admin Guide profiles of tls.cfg file. 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. + deployed in the same folder with 'kamailio.cfg'. For freshly generated + self signed certificates make must be called from tls folder +make install-tls-cert HINT: be sure you have enable_tls=yes to your kamailio.cfg. @@ -402,9 +403,6 @@ make -C modules/tls extra_defs="-DTLS_WR_DEBUG -DTLS_RD_DEBUG" standard conforming (the verification should happen during TLS connection establishment and not after). - TLS specific config reloading is not safe, so for now better don't use - it, especially under heavy traffic. - This documentation is incomplete. The provided selects are not documented in this file. A list with all the ones implemented by the TLS module can be found in the Cookbook @@ -1683,6 +1681,10 @@ verify_client = optional_no_ca are not terminated and they continue to use the old certificates. The new configuration will be used for new connections. + Reload is generally safe and usable in production environments. If + possible should be done in a time where the service has lower + usage/connections. + This RPC command is exported with "RPC_EXEC_DELTA" flag, therefore its execution rate can be restricted to specific time intervals by setting the "rpc_exec_delta" core parameter.