I propose a patch for app-crypt/qca-ossl-2.0.0_beta3 to prepare for openssl phasing out SSL2 support.
Created attachment 401070 [details, diff]
patch for ebuild
Created attachment 401072 [details, diff]
*** Bug 546326 has been marked as a duplicate of this bug. ***
When we introduce any USE=ssl2 we may do so concurrently in all the relevant packages, see blocker #510798 therefore.
There is a commit upstream that looks like it would let us do openssl[ssl2=] if/when that flag's introduced. It's part of qca[openssl] which replaces qca-ossl.
I wonder why this blocks 510798. Imho this should depend on it.
plugins/qca-ossl/qca-ossl.cpp now has:
ctx = SSL_CTX_new(SSLv2_client_method());
ctx = SSL_CTX_new(SSLv3_client_method());
should we now add sslv2 and sslv3 USE flags to qca with the appropriate USE dep on openssl?
@kensington: Thanks for your hint. Use flags are no longer needed.