1158ff67b4
QSslCertificate::verify() has an undocumented and not very desirable property - on some platorms it updates the default configuration, which can be surprising. For example, we deprecated QSslSocket::setDefaultCaCertificates() and recommend using QSslConfiguration::defaultConfiguration(), QSslConfiguration::setDefaultConfiguration(), and QSslConfiguration::setCaCertificates(). If an application does this to select CA roots it trusts explicitly, and then for some reason is calling verify, the application can have its QSslSockets successfully connecting to a host, whose root was not trusted by the application. Also, on Windows, defaultCaCertificates() include system roots already, no need to have them twice. [ChangeLog][QtCore][QtNetwork] QSslSocket::verify - do not change the default configuration Pick-to: 5.15 Pick-to: 6.0 Pick-to: 6.0.0 Fixes: QTBUG-88639 Change-Id: I1cd40b259d0a6dcd15c78d1e7c027ff10859595c Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io> |
||
---|---|---|
.. | ||
127-0-0-1-as-CN.crt | ||
aspiriniks.ca.crt | ||
bogus-ca.crt | ||
bogus-ca.key | ||
bogus-client.crt | ||
bogus-client.key | ||
bogus-server.crt | ||
bogus-server.key | ||
ca.crt | ||
fake-login.live.com.key | ||
fake-login.live.com.pem | ||
fluke.cert | ||
fluke.key | ||
inter.crt | ||
leaf.crt | ||
leaf.key | ||
qt-test-server-cacert.pem | ||
qt-test-server-cert.pem | ||
qtiochain.crt | ||
selfsigned-client.crt | ||
selfsigned-client.key | ||
selfsigned-server.crt | ||
selfsigned-server.key | ||
subjectAltNameIP.crt | ||
xn--schufele-2za.crt |