diff options
author | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2017-02-01 13:55:32 +0100 |
---|---|---|
committer | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2017-02-11 16:18:49 +0000 |
commit | 17927392cf1cecb20cef7cb9cd77131391de087c (patch) | |
tree | e21bba8d6a99c97ac6f7dbb88b089d2cd479bccb /src/network/ssl/qsslsocket_openssl_symbols.cpp | |
parent | 364b161122b567e3a6f7343d438fb540b9fb7e5c (diff) |
Allow Secure Transport backend to use a temporary keychain
Since day one Secure Transport socket has two annoying problems on macOS:
when we call SecPKCS12Import, we indeed import certs and keys into the default keychain
and also (which is more serious) later a dialog can pop up, asking for permission
to use a private key (this is especially annoying if you're running SSL autotests or
have a server application). Apparently, it's possible to work around those problems
if we create our own (temporary) keychain and pass it in the 'options' parameter
to SecPKCS12Import.
[ChangeLog][QtNetwork] Allow QSslSocket to use a temporary keychain on macOS.
Task-number: QTBUG-56102
Change-Id: Ic3a56c905100dc80d907a25fe6ebfa232dcf5b9e
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Diffstat (limited to 'src/network/ssl/qsslsocket_openssl_symbols.cpp')
0 files changed, 0 insertions, 0 deletions