thanks for the info - so I'll exclude verify from my encrpyt() code for
iOS and rely on sslErrors() for the errorlist
in encrypt() I still can do some checks on certificate chain by myself
ekke
Am 28.02.20 um 10:12 schrieb Mårten Nordheim:
Yes, it’s not implemented. Not 100% sure on the details but I believe
there’s some missing API, so it hasn’t been seen as feasible to implement.
https://github.com/qt/qtbase/blob/5.15/src/network/ssl/qsslsocket_mac.cpp#L629
Now Secure transport is “considered legacy” from Apple’s side. What
this means is not certain, but we’re probably not getting new API :(
https://developer.apple.com/documentation/security/secure_transport
Mårten
*From: *ekke <mailto:e...@ekkes-corner.org>
*Sent: *fredag 28. februar 2020 09:26
*To: *interest@qt-project.org <mailto:interest@qt-project.org>
*Subject: *[Interest] QSslCertificate verify unimplemented on iOS ?
I'm using QSslCertificate::verify successfully on Android
QList <https://doc.qt.io/qt-5/qlist.html><QSslError
<https://doc.qt.io/qt-5/qsslerror.html>>
QSslCertificate::verify(QList
<https://doc.qt.io/qt-5/qlist.html><QSslCertificate
<https://doc.qt.io/qt-5/qsslcertificate.html#QSslCertificate>>
/certificateChain/, const QString
<https://doc.qt.io/qt-5/qstring.html> &/hostName/ = QString())
Doing the same on iOS I'm getting "Unimplemented Code" logged and the
list contains one entry "unknown error"
is this expected behaviour ?
thx
ekke
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
