> > > Can anyone send me hint how to provide backward compatibility at least to > > > 10.13 (fixing the symbol issue) or lower (fixing the SSL issue) ? > > > > You didn't say what symbols they were. > > Sorry - this is the one which was reported most of the time: > > __chkstd_darwin
Correction: it is __chdstk_darwin -- http://www.carot.de Email : alexan...@carot.de Tel.: +49 (0)177 5719797 > Gesendet: Sonntag, 02. August 2020 um 20:08 Uhr > Von: "Alexander Carôt" <alexander_ca...@gmx.net> > An: "Thiago Macieira" <thiago.macie...@intel.com> > Cc: interest@qt-project.org > Betreff: Re: [Interest] Win:TLS error/OSX:backward compatibility > > > That warning is printed when you try to use one of the QSslSocket functions > > that require OpenSSL and the OpenSSL libraries are not found. > > > > Make sure QSslSocket::supportSsl() returns true. You have to ship the > > OpenSSL > > 1.1 libraries yourself, they are not part of Qt, not even of the pre-built > > binaries. > > > Allright - will do so. > > > > > 2.) In order to provide backward compatibility on OSX I am typically > > > providing two versions: 10.15 and 10.14 are being compiled with the recent > > > version of Qt. This binary launches with 10.13 but throws an errors about > > > missing symbols in libSystem.B.dylib > > > > Are you sure you built Qt with a minimum target version of 10.13? > > My pro-File contains: > > QMAKE_MAC_SDK = macosx10.15 > QMAKE_CFLAGS_RELEASE = "-mmacosx-version-min=10.13" > QMAKE_CXXFLAGS_RELEASE = "-mmacosx-version-min=10.13" > > > > Qt 5.9 cannot do SSL/TLS in 2020 outside of a Mac. You must upgrade to 5.10 > > at > > a minimum. On a Mac, because Qt has used SecureTransport for years, it can > > work. But it could have issues I am not aware of. > > > OK - thanks for sharing this info ! > > > > Either way, Apple stopped supporting 10.12 last year. > > > So - I believe I should use 10.13 as the lowest supported version. > > > > > Can anyone send me hint how to provide backward compatibility at least to > > > 10.13 (fixing the symbol issue) or lower (fixing the SSL issue) ? > > > > You didn't say what symbols they were. > > Sorry - this is the one which was reported most of the time: > > __chkstd_darwin > > There might be others but this would be a good starting point. > > Best > > Alex > > > > > -- > > Thiago Macieira - thiago.macieira (AT) intel.com > > Software Architect - Intel DPG Cloud Engineering > > > > > > > > _______________________________________________ > > Interest mailing list > > Interest@qt-project.org > > https://lists.qt-project.org/listinfo/interest > > > > -- > http://www.carot.de > Email : alexan...@carot.de > Tel.: +49 (0)177 5719797 > > > > Gesendet: Sonntag, 02. August 2020 um 19:31 Uhr > > Von: "Thiago Macieira" <thiago.macie...@intel.com> > > An: interest@qt-project.org > > Betreff: Re: [Interest] Win:TLS error/OSX:backward compatibility > > > > On Saturday, 1 August 2020 00:13:21 PDT Alexander Carôt wrote: > > > Hello all, > > > > > > my software's websocket server is now running in secure mode including > > > certificate integration. This works great apart from two details. > > > > > > 1.) On some Windows machines I get the following error: > > > > > > qt.network.ssl: QSslSocket::startServerEncryption: TLS initialization > > > failed > > > > > > I believe there are some missing libs on these machine but I am not sure > > > how > > > to resolve this issue conveniently. > > > > That warning is printed when you try to use one of the QSslSocket functions > > that require OpenSSL and the OpenSSL libraries are not found. > > > > Make sure QSslSocket::supportSsl() returns true. You have to ship the > > OpenSSL > > 1.1 libraries yourself, they are not part of Qt, not even of the pre-built > > binaries. > > > > > 2.) In order to provide backward compatibility on OSX I am typically > > > providing two versions: 10.15 and 10.14 are being compiled with the recent > > > version of Qt. This binary launches with 10.13 but throws an errors about > > > missing symbols in libSystem.B.dylib > > > > Are you sure you built Qt with a minimum target version of 10.13? > > > > > For 10.12 and lower I am compiling my app with Qt version 5.9 which works > > > a > > > usual but the new encryption calls obviously don't. With this version the > > > SSL handshake between browser and app fails. > > > > Qt 5.9 cannot do SSL/TLS in 2020 outside of a Mac. You must upgrade to 5.10 > > at > > a minimum. On a Mac, because Qt has used SecureTransport for years, it can > > work. But it could have issues I am not aware of. > > > > Either way, Apple stopped supporting 10.12 last year. > > > > > Can anyone send me hint how to provide backward compatibility at least to > > > 10.13 (fixing the symbol issue) or lower (fixing the SSL issue) ? > > > > You didn't say what symbols they were. > > > > -- > > Thiago Macieira - thiago.macieira (AT) intel.com > > Software Architect - Intel DPG Cloud Engineering > > > > > > > > _______________________________________________ > > Interest mailing list > > Interest@qt-project.org > > https://lists.qt-project.org/listinfo/interest > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest > _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
