Timur Pocheptsov 3e1758e35d QSsl: do not wait for 'connected'/'encrypted' if a protocol is disabled ... since we'll refuse to continue with a handshake, failing in initSslContext() on a disabled protocol versions. Then, functions like waitForEncrypted, connectToHostEncrypted, startServerEncryption and startClientEncryption should either bail out early (who needs a TCP connection which we'll abort anyway?) or bail out whenever we can, as soon as a disabled protocol was found in a configuration. This change also makes the behavior of different back-ends consistent, since it's a general code-path that reports the same SslInvalidUserData error. Update auto-test to ... actually test what it claims it tests. Task-number: QTBUG-72196 Task-number: QTBUG-72179 Change-Id: I548468993410f10c07ce5773b78f38132be8e3e0 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>		2018-12-21 03:28:47 +00:00
..
access	Merge remote-tracking branch 'origin/5.12' into dev	2018-12-04 09:58:43 +01:00
bearer	Make tests compile for Android	2018-06-25 08:01:19 +00:00
kernel	tst_qnetworkinterface: Fix for case of zero interface	2018-07-06 06:39:36 +00:00
socket	Merge remote-tracking branch 'origin/5.11' into 5.12	2018-11-27 01:00:09 +01:00
ssl	QSsl: do not wait for 'connected'/'encrypted' if a protocol is disabled	2018-12-21 03:28:47 +00:00
network.pro	…