Secure Transport relies on keychains, both client/server are constantly updating default keychain and as a result tests are failing: when verification is expected to fail, it succeeds; when the number of certificates is expected to be 1 - it's 2 (Secure Transport can find certificates in a keychain). This makes verifyClientCertificate test quite useless at the moment - QSKIP it. Change-Id: I578398b4912a86dc60f585ac5a1bdd0098914005 Reviewed-by: Richard J. Moore <rich@kde.org> |
||
|---|---|---|
| .. | ||
| certs | ||
| .gitignore | ||
| BLACKLIST | ||
| qsslsocket.pro | ||
| ssl.tar.gz | ||
| tst_qsslsocket.cpp | ||