I was using the system Qt actually but even it sees and accepts system provided LibreSSL as soon as I try to;
QNetworkReply *reply = mgr.get(req); it gives segfault and traces go from SSL_Library_init etc... even if the url is not a https url... On Mon, Jun 29, 2015 at 9:07 PM, Thiago Macieira <[email protected]> wrote: > On Monday 29 June 2015 16:44:28 NoMercy wrote: > > Hello everyone, > > as a last measure of resort due to desperate endless online searches, I'm > > asking to you if it is possible to not even try to load the system > provided > > SSL Library, instead maybe locally provided libssl.so & libcrypto.so > files? > > Sure, it is possible. > > > Yes the target system is a freebsd and it has the d*mn LibreSSL as > default > > and if you try to change it to OpenSSL (which QT can talk) it's depencies > > are, well practically all the system ;) > > > > Do I really have to statically recompiile all the Qt5 just for this? > (don't > > even know if it'll help) > > If you're using a system Qt, it stands to reason that the system Qt has all > its necessary dependencies installed. So this would not be causing you > trouble. Therefore, I conclude you're not using a system-wide Qt. > > You must be using a Qt deployed alongside your application. You can then > just > modify qsslsocket_openssl_symbols.cpp to search for your deployed > libssl.so.1 > and libcrypto.so.1. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Interest mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/interest >
_______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
