I've removed SSLv3 from the list of supported crypto protocols in
Erlang. This should apply only for cases where application doesn't
define explicitly a list of supported protocols. E.g. if your package
explicitly enables SSLv3 then it will be available, otherwise - won't
be. The packages are available in testing repositories:
I'm pretty sure this won't break things which weren't broken already.
However I've heard a bizarre report about RabbitMQ failure when using
Erlang with SSlv3 disabled against some 3rd party crypto tool:
I would be thankful for the testing of RabitMQ against these new Erlang builds.
My next goal is to audit CouchDB, Ejabberd, RabbitMQ packages and
remove any SSLv3 traces from them (or even disable explicitly if
possible/necessary). Just fyi.
With best regards, Peter Lemenkov.