After some further research, I've discoverred that adding:
modparam("tls", "tls_force_run", 1)
to kamailio.cfg allows kama to start, so the bug probably is a bit less
severe than grave. Testing shows that such an addition does allow kam
to not only start, but actually use tls.
That being said
Source: kamailio
Version: 4.2.0-2
Severity: grave
Justification: renders package unusable
Today's upgrade to openssl 1.0.2 means that kamailio cannot start when using
the tls module.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'e
2 matches
Mail list logo
