https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #8 from Matt Fagnani <matt.fagn...@bell.net> ---
I bisected this problem with qca from 2.3.7 to 2.3.8. The following first bad
commit involved loading legacy openssl providers.
14eb1ae746c3c75afaef02b487ac65b3de85ad15 is the first bad commit
commit 14eb1ae746c3c75afaef02b487ac65b3de85ad15
Author: Fabian Vogt <fab...@ritter-vogt.de>
Date: Fri Dec 22 13:36:00 2023 +0100
plugins/qca-ossl: Actually try loading the legacy provider
OSSL_PROVIDER_available returns true only for loaded providers, not whether
a provider can be loaded. Use OSSL_PROVIDER_try_load instead, which also
allows to keep the default fallback provider.
plugins/qca-ossl/qca-ossl.cpp | 24 +++++-------------------
1 file changed, 5 insertions(+), 19 deletions(-)
--
You are receiving this mail because:
You are watching all bug changes.
