Using QSslSocket with custom OpenSSL
-
wrote on 14 Sept 2016, 16:24 last edited by
You cannot use the pre-built binary of Qt, you'll have to compile it yourself linking to the new OpenSSL
-
wrote on 14 Sept 2016, 16:42 last edited by
That's a lot of work! So what if I want to use what Qt offers me? Why QSslSocket::supportsSsl() returns false?
-
I want to use QSslSocket and QSslCertificate with my latest OpenSSL build. I built OpenSSL 1.1.0 with VS2015 and added its bin directory into %PATH, also added its LIBS to my .pro file:
LIBS += -LC:/openssl_1.1.0/lib/ -llibcrypto -llibsslWhen I run my application, QSslSocket::supportsSsl() returns false and QSslSocket::sslLibraryBuildVersionString() returns OpenSSL 1.0.2g 1 Mar 2016, even though I built OpenSSL 1.1.0. Also I get error messages like this:
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_errorWhat is the problem? How can I use my built OpenSSL libraries and binaries?
P.S. I use Windows 10, Qt 5.7, OpenSSL 1.1.0, Visual Studio 2015 Enterprise.
Thank you
@MChelik
Qt loads the OpenSSL libs on demand. Where the DLL name is hardcoded and the methods are resolved "manually".
So linking against OpenSSL wont make any difference. -
wrote on 14 Sept 2016, 16:48 last edited by
@raven-worx So why QSslSocket::supportsSsl() returns false? Lets forget about my custom OpenSSL.
-
wrote on 14 Sept 2016, 16:56 last edited by
did you add the OpenSSL path to PATH?
-
@MChelik
on windows they are called ssleay32.dll and libeay32.dll -
@MChelik
on windows they are called ssleay32.dll and libeay32.dllwrote on 14 Sept 2016, 18:40 last edited by@raven-worx Since QSslSocket::sslLibraryBuildVersionString() returns "OpenSSL 1.0.2g 1 Mar 2016", I downloaded OpenSSL_1.0.2g source code and compiled it, but inside bin directory there was only openssl.exe. So I copied ssleay32.dll and libeay32.dll from C:\Qt\Tools\QtCreator\bin to C:\Windows. But still I get same error, nothing changed.
What should I do use QSslSocket? I'm really confused. I searched a lot but nothing helped. -
Hi and welcome to devnet,
Don't copy .dlls like that in the Windows folder, that's very bad practice.
If Qt shows you a different version of OpenSSL, it likely means that you have an application that also provides these files and can be found before yours.
I've successfully used the prebuilt packages from Shining Lights Production.
Hope it helps
-
@raven-worx Since QSslSocket::sslLibraryBuildVersionString() returns "OpenSSL 1.0.2g 1 Mar 2016", I downloaded OpenSSL_1.0.2g source code and compiled it, but inside bin directory there was only openssl.exe. So I copied ssleay32.dll and libeay32.dll from C:\Qt\Tools\QtCreator\bin to C:\Windows. But still I get same error, nothing changed.
What should I do use QSslSocket? I'm really confused. I searched a lot but nothing helped.@MChelik said in Using QSslSocket with custom OpenSSL:
So I copied ssleay32.dll and libeay32.dll from C:\Qt\Tools\QtCreator\bin to C:\Windows
don't do that, as @SGaist said. Copy them next to your application exe instead.
-
wrote on 16 Sept 2016, 00:21 last edited by
Thank you SGaist. Copying next to application executable didn't help either.
Gentlemen, let's forget my OpenSSL; forget everything. Just assume that I want to use QSslSocket and QSslCertificate. What should I do? Should I compile Qt myself? Should I install OpenSSL? What should I do exactly? Qt documents doesn't say any specific thing about this. Documents say only how to use mentioned two classes.
Thank you -
wrote on 16 Sept 2016, 01:06 last edited by hskoglund
Hi, just a quick note on OpenSSL with Qt, I think because you're building a 64-bit Qt app that's why you're having problems. Because those 2 DLLs s stored in C:\Qt\Tools\QtCreator\bin are built with MSVC2013 32-bit compiler (same as for Qt Creator itself) so they are not kosher for 64-bit :-(
-
To add to @hskoglund, the prebuilt packages I've mentioned earlier also provide "OpenSSL-Win64" which are pre-built for 64bit development.
-
wrote on 17 Sept 2016, 23:51 last edited by
@hskoglund That was my problem! I didn't pay attention to that. But I a have a question: The only libeay32.dll and ssleay32.dll files that are in my %PATH% is C:\Win64-OpenSSL\bin directory. So why my application only works when mentioned DLLs are beside my application (doesn't work when are in %PATH)?
-
Are you sure you don't have any other application that has these libraries and that can be found in your PATH environment variable ?
-
Are you sure you don't have any other application that has these libraries and that can be found in your PATH environment variable ?
-
How did you modify PATH ? In your Windows settings or in Qt Creator ?
-
wrote on 19 Sept 2016, 22:04 last edited by
Hi, also, they could be loaded via some other means than their directories being listed in %PATH%, either that some other dll that your .exe loads explicitly pulls in the bad (i.e. 32-bit) ones, or perhaps they're hiding in c:\windows or c:\windows\system32.
To debug this. you could try download Dependency Walker and load your app into it. Then start profiling with F7, that'll get you a trace of all the dlls loaded.
-
wrote on 20 Sept 2016, 14:31 last edited byThis post is deleted!
-
This post is deleted!
wrote on 20 Sept 2016, 15:12 last edited byThis post is deleted!
11/41