Closed #1492.
--
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/1492#event-1556172938___
Kamailio (SER) - Development Mailing List
1. Yes - HSM private keys are stored in worker local memory and are not
referenced in old structures during SIP connections. We make one reference
during mod_child: we install it into the shmem SSL_CTX structure once (proc_no
== 0) just to check the the private key corresponds to the cert;
Module: kamailio
Branch: 5.1
Commit: 6770fe866dc6ed301b536a6132dc50e9844e720e
URL:
https://github.com/kamailio/kamailio/commit/6770fe866dc6ed301b536a6132dc50e9844e720e
Author: Lucian Balaceanu
Committer: Lucian Balaceanu
Date:
Hi @lbalaceanu . I rebuilt kamailio 5.1.2 with your fix. Problem solved. I
think you can close issue. Thank you.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hello,
2018-04-03 23:03 GMT+02:00 Daniel-Constantin Mierla :
> changes expected to affect packaging should be discussed first and then
> committed, along with related updates to packaging specs.
>
> They can break nightly builds for packages, resulting in unnecessary
> alerts
* About the question:
"The files tls_map.{c,h} seems to be imported from external source, being
under MIT license. tls
module seems to be under BSD, anyone knows if there is any conflict between
the two or
something needs to be mentioned in the README of the tls module?"
Module: kamailio
Branch: master
Commit: 7db5d4c4efb2131a7393e638f109ddbe746ffeff
URL:
https://github.com/kamailio/kamailio/commit/7db5d4c4efb2131a7393e638f109ddbe746ffeff
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date:
Module: kamailio
Branch: master
Commit: 8f9b6ea5637b26092e591585b82eb59ed2f42775
URL:
https://github.com/kamailio/kamailio/commit/8f9b6ea5637b26092e591585b82eb59ed2f42775
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date:
If there are 3 servers, then the step should at least 3, resulting in:
```
Server1: 1, 4, 7, 10, ...
Server2: 2, 5, 8, 11, ...
Server3: 3, 6, 9, 12, ...
```
So the start value should be the `index` of the server and the increment value
has to be at least the number of servers. There is no
In our case we will have an autoscaling system of Kamailio based on geographic
requests and load so we will not be able to know in advance how many instances
ok kamailio will be provisioned. As you suggested for this temporary workaround
we should have :
Server 1 : 1, 101,201,301,401...
Server
Am Dienstag, 3. April 2018, 22:59:42 CEST schrieb Daniel-Constantin Mierla:
> > I will change it to involve only security bugs, this way we could easily
> > change it when we have a dedicated security contact address. If we get to
> > much spam, I will remove it completely.
>
> I still think this
The problem is with the reset of a prefix options structure. This is due to a
recent change in the code. I will come up with a fix.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1494
-- Commit Summary --
* pkg/kamailio/obs: packaged db_redis module
* pkg/kamailio/obs: Added acc_json module
* pkg/kamailio/obs: Added pua_json module
* pkg/kamailio/obs:
I have pushed
https://github.com/kamailio/kamailio/commit/dc8faaf57a9c85b7133f112bdedd328a9520eb73
on the master branch. For me it solved the problem. Could you confirm that
this is also the case for you so that we can close the issue?
--
You are receiving this because you are subscribed to
Module: kamailio
Branch: master
Commit: f7ed7d289978490f374f4f3eea52e91dccc3752f
URL:
https://github.com/kamailio/kamailio/commit/f7ed7d289978490f374f4f3eea52e91dccc3752f
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date:
Module: kamailio
Branch: master
Commit: 3d3f5ca116353cc618f52d5c2792f360377a63ca
URL:
https://github.com/kamailio/kamailio/commit/3d3f5ca116353cc618f52d5c2792f360377a63ca
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date:
Module: kamailio
Branch: master
Commit: b27475511756b04fe4d4ee5f76bcc14e4186bc58
URL:
https://github.com/kamailio/kamailio/commit/b27475511756b04fe4d4ee5f76bcc14e4186bc58
Author: Kamailio Dev
Committer: Kamailio Dev
Date:
I just committed the config (and kemi) function `dlg_db_load_callid(val)`,
which should load dialog record from database by matching on callid (it loads
also associated variables).
While not tested yet given lack of proper environment to simulate such scenario
(hopefully you can do it), there
Just to confirm I haven't missed something -- the private keys stored in
worker-local memory refer to keeping them in the map structure you introduced
with the new files tls_map.{c,h}. They are not referenced from old structures
of the tls module, right?
I see that the define conditions are on
Module: kamailio
Branch: master
Commit: 0180884c6111b6a1d88fc558acbc801718c011b8
URL:
https://github.com/kamailio/kamailio/commit/0180884c6111b6a1d88fc558acbc801718c011b8
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date:
Thanks! One question before attempting to merge, does this require a specific
version of redis server or redis client library?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
After a quick look on redis website the sentinel is shipped with redis since
2.8 so I suppose this is the minimum required but if the sentinel options are
not used the driver should work as before with any redis version.
--
You are receiving this because you are subscribed to this thread.
Module: kamailio
Branch: master
Commit: dc8faaf57a9c85b7133f112bdedd328a9520eb73
URL:
https://github.com/kamailio/kamailio/commit/dc8faaf57a9c85b7133f112bdedd328a9520eb73
Author: Lucian Balaceanu
Committer: Lucian Balaceanu
Date:
23 matches
Mail list logo