1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify the priority in selecting TLS backends

Browse Source 
In case a custom TLS plugin is provided, the order can be unclear
(next after OpenSSL is either Schannel on Windows, or Secure Transport
on Darwin, then a custom plugin, if any, and the last one is 'cert-only').

Pick-to: 6.7 6.6 6.5 6.2
Fixes: QTBUG-123092
Change-Id: I02bcc1fa5448f64846d561a72b2522af3286c66c
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
This commit is contained in:
Timur Pocheptsov 2024-03-20 15:45:32 +01:00
parent fbcd223507
commit 128645d023
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/network/ssl/qsslsocket.cpp
View File

@ -1544,7 +1544,12 @@ QList<QString> QSslSocket::availableBackends()
from the list of available backends.
\note When selecting a default backend implicitly, QSslSocket prefers
the OpenSSL backend if available.
the OpenSSL backend if available. If it's not available, the Schannel backend
is implicitly selected on Windows, and Secure Transport on Darwin platforms.
Failing these, if a custom TLS backend is found, it is used.
If no other backend is found, the "certificate only" backend is selected.
For more information about TLS plugins, please see
\l {Enabling and Disabling SSL Support when Building Qt from Source}.
\sa setActiveBackend(), availableBackends()
*/