Wrong version of OpenSSL used when deploying application

[rctm]

My Application is running fine when launched from QtCreator, but can't run from console.
Error when ran from console:

qt.tlsbackend.ossl: Incompatible version of OpenSSL (built with OpenSSL >= 3.x, runtime version is < 3.x)
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslSocket
qt.network.ssl: The backend named "cert-only" does not support TLS
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed

.pro file:

    LIBS += -L/usr/local/lib64 -lcrypto  -lssl

ldd application output:

        libcrypto.so.3 => /usr/local/lib64/libcrypto.so.3 (0x00007face2a90000)
        libssl.so.3 => /usr/local/lib64/libssl.so.3 (0x00007face29d9000)

How can I tell Qt which library to use when deploying my application?
OS is debian 9 and OpenSSL 3.2.0-dev is installed.
QT version is 6.5.2.

[kkoehne]

@rctm When openssl is loaded at runtime, Qt does not use ld. Instead, it checks out directories in LD_LIBRARY_PATH, and some default locations (/lib, /usr/lib , /usr/local/lib , as well the lib32 and lib64variants:

https://codebrowser.dev/qt5/qtbase/src/network/ssl/qsslsocket_openssl_symbols.cpp.html#_ZL15libraryPathListv

So augmenting /etc/ld.so.conf won't make a difference.

[JoeCFD]

@rctm you wrap these libs with your app and deploy it, just like Qt libs.

[rctm]

@JoeCFD In my understanding I've already done that here:
ldd output of built application:

libcrypto.so.3 => /usr/local/lib64/libcrypto.so.3 (0x00007face2a90000)
libssl.so.3 => /usr/local/lib64/libssl.so.3 (0x00007face29d9000)

qt.tlsbackend.ossl: Incompatible version of OpenSSL (built with OpenSSL >= 3.x, runtime version is < 3.x)

Like it's saying here my runtime version is too low, but OpenSSL 3.2.0 is installed.
Since it works fine in QTCreator I'm thinking it has to be some kind of configuration problem. Is there a setting I'm missing?

[Christian Ehrlicher]

Since the openssl libs are loaded dynamically on runtime the linker will not help here. I would guess QtCreator is setting the LD_LIBRARY_PATH accordingly so the correct openssl libs are loaded during runtime.

[rctm]

@Christian-Ehrlicher said in Wrong version of OpenSSL used when deploying application:

LD_LIBRARY_PATH

Thank you! I can now run the application from terminal if I add the path of the openssl libs to LD_LIBRARY_PATH.
Whats weird is that I've already added this path to /etc/ld.so.conf and ran ldconfig, so the path should already be known.

[JonB]

@rctm
Only a guess here. If you are saying you have a different version of the library on LD_LIBRARY_PATH then maybe ld.so.conf only adds an extra place to look by default after LD_LIBRARY_PATH, you have to insert your desired location earlier in LD_LIBRARY_PATH to prevent the other one being found first?

[kkoehne]

@rctm When openssl is loaded at runtime, Qt does not use ld. Instead, it checks out directories in LD_LIBRARY_PATH, and some default locations (/lib, /usr/lib , /usr/local/lib , as well the lib32 and lib64variants:

https://codebrowser.dev/qt5/qtbase/src/network/ssl/qsslsocket_openssl_symbols.cpp.html#_ZL15libraryPathListv

So augmenting /etc/ld.so.conf won't make a difference.