<!-- 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
added RPID header parser to extract URL's user and store to PPI field.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1653
-- Commit Summary --
* module/sipcapture: added RPID parser for PPI field
-- File Changes --
M src/modules/sipcapture/sipcapture.c (11)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1653.patchhttps://github.com/kamailio/kamailio/pull/1653.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1653
Apparently the default locks are set to PTHREAD mutex, when the architecture is not handled explicitely. It should be reviewed and eventually switch to standard POSIX, they should work everywhere while PTHREAD are targeting threads and work only in few cases for processes.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1035
Module: kamailio
Branch: master
Commit: f1f5ec13937ae14aee0c1610dd1dcd2e1100966b
URL: https://github.com/kamailio/kamailio/commit/f1f5ec13937ae14aee0c1610dd1dcd2…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2018-09-27T12:31:37+02:00
modules: readme files regenerated - tls ... [skip ci]
---
Modified: src/modules/tls/README
---
Diff: https://github.com/kamailio/kamailio/commit/f1f5ec13937ae14aee0c1610dd1dcd2…
Patch: https://github.com/kamailio/kamailio/commit/f1f5ec13937ae14aee0c1610dd1dcd2…
---
diff --git a/src/modules/tls/README b/src/modules/tls/README
index 578333ea44..3ea60f8949 100644
--- a/src/modules/tls/README
+++ b/src/modules/tls/README
@@ -91,7 +91,7 @@ Olle E. Johansson
List of Examples
- 1.1. Quick start config
+ 1.1. Quick Start Basic Config
1.2. Compiling TLS with Debug Messages
1.3. Set tls_method parameter
1.4. Set certificate parameter
@@ -223,24 +223,38 @@ Chapter 1. Admin Guide
2. Quick Start
- Make sure you have a proper certificate and private key and either use
- the certificate and private_key module parameters, or make sure the
- certificate and key are in the same PEM file, named cert.pem an placed
- in [your-cfg-install-prefix]/etc/kamailio/. Don't forget to load the
- tls module and to enable TLS (add enable_tls=yes to your config).
+ The default kamailio.cfg file has basic tls support included, it has to
+ be enabled with "#!define WITH_TLS" directive.
- Example 1.1. Quick start config
+ The most important parameters to set the path to the public certificate
+ and private key files. You can either have them in different file or in
+ the same file in PEM format. The parameters for them are certificate
+ and private_key. They can be given as modparam or or provided in the
+ 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.
+
+ HINT: be sure you have enable_tls=yes to your kamailio.cfg.
+
+ Example 1.1. Quick Start Basic Config
#...
-loadmodule "modules/tls/tls.so"
+loadmodule "sl.so"
+loadmodule "tls.so"
-modparam("tls", "private_key", "./andrei-test.pem")
-modparam("tls", "certificate", "./andrei-test.pem")
+modparam("tls", "private_key", "./server-test.pem")
+modparam("tls", "certificate", "./server-test.pem")
modparam("tls", "ca_list", "./calist.pem")
enable_tls=yes
-route{
- # ....
+request_route {
+ if(proto != TLS) {
+ sl_send_reply("403", "Accepting TLS Only");
+ exit;
+ }
+ ...
}
3. Important Notes
@@ -1445,14 +1459,16 @@ modparam("tls", "engine_algorithms", "ALL")
11.1. is_peer_verified()
- Returns true if the connection on which the message was received is TLS
- , the peer presented an X509 certificate and the certificate chain
- verified ok. It can be used only in a request route.
+ Returns true if the connection on which the message was received is
+ TLS, the peer presented an X509 certificate and the certificate chain
+ verified ok.
+
+ It can be used only in a request route.
Example 1.45. is_peer_verified usage
- if (proto==TLS && !is_peer_verified()){
+ if (proto==TLS && !is_peer_verified()) {
sl_send_reply("400", "No certificate or verification failed");
- drop;
+ exit;
}
12. RPC Commands
repro servers peer with each other in a federated manner just like SMTP servers for email, but using TLS mutual authentication to prevent impersonation.
Kamailio has TLS support and should be able to talk to such servers and other Kamailio servers in the same way.
It would be good to create a recommended sample configuration for this type of service and also add it to the RTC Quick Start Guide:
http://rtcquickstart.org/guide/multi/sip-proxy.html
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/531
Module: kamailio
Branch: master
Commit: b08df6d531513ecf472f4642ddf180bffac46f58
URL: https://github.com/kamailio/kamailio/commit/b08df6d531513ecf472f4642ddf180b…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2018-09-27T12:20:39+02:00
tls: updates to overview section
- GH #531
---
Modified: src/modules/tls/doc/functions.xml
Modified: src/modules/tls/doc/tls.xml
---
Diff: https://github.com/kamailio/kamailio/commit/b08df6d531513ecf472f4642ddf180b…
Patch: https://github.com/kamailio/kamailio/commit/b08df6d531513ecf472f4642ddf180b…
---
diff --git a/src/modules/tls/doc/functions.xml b/src/modules/tls/doc/functions.xml
index 1f3116f26d..2a371de8f1 100644
--- a/src/modules/tls/doc/functions.xml
+++ b/src/modules/tls/doc/functions.xml
@@ -18,16 +18,18 @@
<title><function>is_peer_verified()</function></title>
<para>
Returns true if the connection on which the message was received
- is TLS , the peer presented an X509 certificate and the
+ is TLS, the peer presented an X509 certificate and the
certificate chain verified ok.
+ </para>
+ <para>
It can be used only in a request route.
</para>
<example>
<title><function>is_peer_verified</function> usage</title>
<programlisting>
- if (proto==TLS && !is_peer_verified()){
+ if (proto==TLS && !is_peer_verified()) {
sl_send_reply("400", "No certificate or verification failed");
- drop;
+ exit;
}
</programlisting>
</example>
diff --git a/src/modules/tls/doc/tls.xml b/src/modules/tls/doc/tls.xml
index f5337baaf9..8147208f70 100644
--- a/src/modules/tls/doc/tls.xml
+++ b/src/modules/tls/doc/tls.xml
@@ -68,27 +68,41 @@
<section id="tls.quick_start">
<title>Quick Start</title>
<para>
- Make sure you have a proper certificate and private key and either
- use the <varname>certificate</varname> and <varname>private_key</varname>
- module parameters, or make sure the certificate and key are in the same PEM file,
- named <emphasis>cert.pem</emphasis> an placed in [your-cfg-install-prefix]/etc/kamailio/.
- Don't forget to load the tls module and to enable TLS
- (add <emphasis>enable_tls=yes</emphasis> to your config).
+ The default kamailio.cfg file has basic tls support included, it has to
+ be enabled with "#!define WITH_TLS" directive.
+ </para>
+ <para>
+ The most important parameters to set the path to the public certificate and private key
+ files. You can either have them in different file or in the same file in PEM format.
+ The parameters for them are <varname>certificate</varname> and <varname>private_key</varname>.
+ They can be given as modparam or or provided in the profiles of tls.cfg file.
+ </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.
+ </para>
+ <para>
+ HINT: be sure you have <emphasis>enable_tls=yes</emphasis> to your kamailio.cfg.
</para>
<example>
- <title>Quick start config</title>
+ <title>Quick Start Basic Config</title>
<programlisting>
#...
-loadmodule "modules/tls/tls.so"
+loadmodule "sl.so"
+loadmodule "tls.so"
-modparam("tls", "private_key", "./andrei-test.pem")
-modparam("tls", "certificate", "./andrei-test.pem")
+modparam("tls", "private_key", "./server-test.pem")
+modparam("tls", "certificate", "./server-test.pem")
modparam("tls", "ca_list", "./calist.pem")
enable_tls=yes
-route{
- # ....
+request_route {
+ if(proto != TLS) {
+ sl_send_reply("403", "Accepting TLS Only");
+ exit;
+ }
+ ...
}
</programlisting>
</example>