Hi all,

is it possible to add in
http://kamailio.org/docs/modules/4.2.x/modules/tls.html
under the line
>

9.1. tls_method (string)

...
...

If rfc3261 conformance is desired, TLSv1 must be used. For compatibility with older clients SSLv23 is a good option.

Example 1.3. Set tls_method parameter

...
modparam("tls", "tls_method", "TLSv1")
...

<


!!! a warning that the use of SSLv3 susceptibility to POODLE Vulnerability !!!

--
Rainer Piper
Integration engineer
Koeslinstr. 56
53123 BONN
GERMANY
Phone: +49 228 97167161
P2P: sip:rainer@sip.soho-piper.de:5072 (pjsip-test)
XMPP: rainer@xmpp.soho-piper.de

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

SSL 3 is dead, killed by the POODLE attack

The POODLE Attack (CVE-2014-3566)

After more than a week of persistent rumours, yesterday (Oct 14) we finally learned about the new SSL 3 vulnerability everyone was afraid of. The so-called POODLE attack is a problem in the CBC encryption scheme as implemented in the SSL 3 protocol. (Other protocols are not vulnerable because this area had been strengthened in TLS 1.0.) Conceptually, the vulnerability is very similar to the 2011 BEAST exploit. In order to successfully exploit POODLE the attacker must be able to inject malicious JavaScript into the victim's browser and also be able to observe and manipulate encrypted network traffic on the wire. As far as MITM attacks go, this one is complicated, but easier to execute than BEAST because it doesn't require any special browser plugins. If you care to learn the details, you can find them in the short paper or in Adam Langley's blog post.