1 |
The relevant bug is here |
2 |
|
3 |
> |
4 |
> https://bugs.gentoo.org/show_bug.cgi?id=576128 |
5 |
> |
6 |
> If you have sslv2 enabled, your choices are clear: |
7 |
> |
8 |
> 1. high likelihood of wholesale breakage, or |
9 |
> 2. wait a little longer for a proper fix |
10 |
> |
11 |
> Obviously -r1 is ideal as it disables sslv2. If you have it and it |
12 |
> works, leave it in place. |
13 |
> |
14 |
> Everyone else is going to have to make up their own mind, and there's no |
15 |
> sane rational advice that can be given for all, considering what the |
16 |
> choices are above. |
17 |
> |
18 |
|
19 |
Remember that the versions of OpenSSL with SSLv2 can be safe if you disable |
20 |
SSLv2 in the services that use that code, eg, in apache, at a minimum, set; |
21 |
|
22 |
SSLProtocol All -SSLv2 |
23 |
|
24 |
To find out what software is using OpenSSL; |
25 |
|
26 |
# qdepends -Q openssl |
27 |
and then investigate how to disable SSLv2 in each of those with network |
28 |
services. Dont forget to restart! |