Comment # 2 on bug 1172267 from V��t��zslav ������ek

Preliminary scan of packages that failed to build with OpenSSL 3.0 in the
staging:

dd_rescue
neon
nodejs10
qpdf
transmission
-> All have various testsuite failures

libssh
rust
-> cmake couldn't detect the new openssl, shall be fixed by the cmake update
from comment 1.

fipscheck
freerdp
nodejs8
openssh
perl-Net-SSLeay
-> FIPS_mode() is gone.
FIPS_mode() and FIPS_mode_set() were removed and replaced by
EVP_default_properties_is_fips_enabled() and 
EVP_default_properties_enable_fips().
As providers are per-context, the new functions take a library context
(OPENSSL_CTX) parameter

kmbox
kubernetes1.18
-> Unknown failures

libarchive
-> RMD160 test fails, probably because the cipher has been moved to the legacy
provider

memcached
qpid-proton
-> SSL_CTX_load_verify_locations() was deprecated in 3.0 and these packages
compile with -Werror, which causes a build failure.
However, the deprecation was recently reverted in
https://github.com/openssl/openssl/commit/c7f837cfcc5b2e5cd8eeeff82e0245323f206d02,
so these packages should build fine as is.

openssl-3 :-)
-> Seems that 30-test_evp.t fails on occasions

python
python-cryptography
python-ecdsa
python-M2Crypto
python-pycurl:test
python-tornado6
python3
-> All failed in the tests
Some failures are related to the problematic change of EOF handling from
OpenSSL 1.1.1e, which at this time is left in 3.0.0, but the EOF error will be
relaxed before 3.0.0 final (see the thread at
https://mta.openssl.org/pipermail/openssl-project/2020-May/001975.html)