QSslSocket usage throws errors cannot resolve CRYPTO_num_locks etc.
-
wrote on 21 Jan 2020, 09:34 last edited by
Hi,
We have a Qt 5.5.1 app that uses QSslSocket to connect to a https URL.
On RHEL 7.x, this works all right.
However, on RHEL 8 it gives the flowing error:
21.01.2020 14:49:03 QSslSocket: cannot resolve CRYPTO_num_locks
21.01.2020 14:49:03 QSslSocket: cannot resolve CRYPTO_set_id_callback
21.01.2020 14:49:03 QSslSocket: cannot resolve CRYPTO_set_locking_callback
21.01.2020 14:49:03 QSslSocket: cannot resolve ERR_free_strings
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_new_null
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_push
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_free
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_num
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_pop_free
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_value
21.01.2020 14:49:03 QSslSocket: cannot resolve SSL_library_init
21.01.2020 14:49:03 QSslSocket: cannot resolve SSL_load_error_strings
21.01.2020 14:49:03 QSslSocket: cannot resolve SSL_get_ex_new_index
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLv2_client_method
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLv23_client_method
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLv2_server_method
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLv23_server_method
21.01.2020 14:49:03 QSslSocket: cannot resolve X509_STORE_CTX_get_chain
21.01.2020 14:49:03 QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
21.01.2020 14:49:03 QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLeay
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLeay_version
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function SSLeay
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function CRYPTO_num_locks
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function SSL_library_init
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function SSLv23_client_method
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function sk_num
21.01.2020 14:49:03 unsupported date format detectedDo we need any specific TLS package to resolve the above?
Thanks.
-
Hi,
We have a Qt 5.5.1 app that uses QSslSocket to connect to a https URL.
On RHEL 7.x, this works all right.
However, on RHEL 8 it gives the flowing error:
21.01.2020 14:49:03 QSslSocket: cannot resolve CRYPTO_num_locks
21.01.2020 14:49:03 QSslSocket: cannot resolve CRYPTO_set_id_callback
21.01.2020 14:49:03 QSslSocket: cannot resolve CRYPTO_set_locking_callback
21.01.2020 14:49:03 QSslSocket: cannot resolve ERR_free_strings
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_new_null
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_push
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_free
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_num
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_pop_free
21.01.2020 14:49:03 QSslSocket: cannot resolve sk_value
21.01.2020 14:49:03 QSslSocket: cannot resolve SSL_library_init
21.01.2020 14:49:03 QSslSocket: cannot resolve SSL_load_error_strings
21.01.2020 14:49:03 QSslSocket: cannot resolve SSL_get_ex_new_index
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLv2_client_method
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLv23_client_method
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLv2_server_method
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLv23_server_method
21.01.2020 14:49:03 QSslSocket: cannot resolve X509_STORE_CTX_get_chain
21.01.2020 14:49:03 QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
21.01.2020 14:49:03 QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLeay
21.01.2020 14:49:03 QSslSocket: cannot resolve SSLeay_version
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function SSLeay
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function CRYPTO_num_locks
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function SSL_library_init
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function SSLv23_client_method
21.01.2020 14:49:03 QSslSocket: cannot call unresolved function sk_num
21.01.2020 14:49:03 unsupported date format detectedDo we need any specific TLS package to resolve the above?
Thanks.
@Sahil_Rangari Did you install OpenSSL?
-
@Sahil_Rangari Did you install OpenSSL?
wrote on 21 Jan 2020, 10:39 last edited byopenssl version gives "OpenSSL 1.1.1 FIPS" with date few months back.
-
openssl version gives "OpenSSL 1.1.1 FIPS" with date few months back.
@Sahil_Rangari If I'm not mistaken you need OpenSSL 1.0.x for that old Qt version
-
wrote on 23 Jan 2020, 09:11 last edited by
Hi,
If I install compat-openssl10.x86_64, the application works as desired.
Should this be an acceptable solution for RHEL 8.0?Thanks.
-
Hi,
If I install compat-openssl10.x86_64, the application works as desired.
Should this be an acceptable solution for RHEL 8.0?Thanks.
@Sahil_Rangari The OpenSSL version you need depends on your Qt version. When using older Qt versions you need 1.0.x, with newer versions you need 1.1.x.
So, yes I think this solution should be OK.
1/6