diff options
| author | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2019-01-24 13:10:02 +0100 |
|---|---|---|
| committer | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2019-01-24 20:38:14 +0000 |
| commit | a90a238b498bd6e219bd805e4e5ddb33278cc49a (patch) | |
| tree | 53ecf15e87f4f2547a0ec5f2550dd1add320c2d5 /tests | |
| parent | 25133a1b77c059e32760f3d288c985183d86da4a (diff) | |
tst_qsslsocket - blacklist several test temporarily
For some reason behavior of SecureTransport has changed from 10.12 to 10.13
and then to 10.14. On 10.13 SecureTransport fails upon receiving the server's
certificate with 'Unrecoverable error', before we can do a manual verification
and accept the certificate as trusted. Analysis of available source code
shows that they, apparently, do not like MD5 hash which our server is using.
Until certificate is updated on the server or we switch completely to
the Docker-based solution we have to BLACKLIST tests that connect to our
current network test-server. Oddly enough, on 10.14 SecureTransport is
less mean.
Task-number: QTBUG-69873
Change-Id: I7da1883e0970a2f6ddd8385f193b76116d6983e0
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/auto/network/ssl/qsslsocket/BLACKLIST | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/tests/auto/network/ssl/qsslsocket/BLACKLIST b/tests/auto/network/ssl/qsslsocket/BLACKLIST index 8e1a55995e..555822d1e6 100644 --- a/tests/auto/network/ssl/qsslsocket/BLACKLIST +++ b/tests/auto/network/ssl/qsslsocket/BLACKLIST @@ -1 +1,7 @@ windows +[connectToHostEncrypted] +osx-10.13 +[setSslConfiguration] +osx-10.13 +[connectToHostEncryptedWithVerificationPeerName] +osx-10.13 |