SSL errors shown on Fedora32 while downloading

[ashishsingh18]

Downloads work under Fedora32 (fast, good progress bar, correct handling of multiple queued download requests).

SSL messages are still present:

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: Incompatible version of OpenSSL

Originally posted by @MarkBergman-cbica in https://github.com/CBICA/CaPTk/pull/1275#issuecomment-687281023

[ashishsingh18]

Thoughts on how to handle this @CBICA/devteam

[AlexanderGetka-cbica]

Is this really something we want to handle? Shouldn't users be informed if SSL-based downloads will fail on their machine? If anything we should add a clarifying error message.

[ashishsingh18]

These ssl messages don't seem to be coming from our code but from Qt classes. We will need access to the Fedora system to better debug this. Reading up more on this here. It seems that this issue was resolved by installing libssl1.0-dev

[sarthakpati]

Can we push the errors to a separate text file (the way we do for VTK)?