From 0192630f55bb62bd7cf3a1dc29c6c0624ca7759c Mon Sep 17 00:00:00 2001 From: Giuseppe D'Angelo Date: Fri, 7 Nov 2014 11:13:12 +0100 Subject: QNetworkAccessManager: introduce support for TLS PSK Expose the same kind of TLS PSK client support we already have set in place for QSslSocket. [ChangeLog][QtNetwork][QNetworkAccessManager] It is now possible to use TLS PSK ciphersuites when using HTTPS (or similar protocols working over SSL). Change-Id: I56a048e9f4f841f886758c781af2867d18538a3e Reviewed-by: Richard J. Moore --- src/network/access/qnetworkreply.cpp | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) (limited to 'src/network/access/qnetworkreply.cpp') diff --git a/src/network/access/qnetworkreply.cpp b/src/network/access/qnetworkreply.cpp index 1710af723f7..67407cd500f 100644 --- a/src/network/access/qnetworkreply.cpp +++ b/src/network/access/qnetworkreply.cpp @@ -253,6 +253,28 @@ QNetworkReplyPrivate::QNetworkReplyPrivate() sslConfiguration(), ignoreSslErrors() */ +/*! + \fn void QNetworkReply::preSharedKeyAuthenticationRequired(QSslPreSharedKeyAuthenticator *authenticator) + \since 5.5 + + This signal is emitted if the SSL/TLS handshake negotiates a PSK + ciphersuite, and therefore a PSK authentication is then required. + + When using PSK, the client must send to the server a valid identity and a + valid pre shared key, in order for the SSL handshake to continue. + Applications can provide this information in a slot connected to this + signal, by filling in the passed \a authenticator object according to their + needs. + + \note Ignoring this signal, or failing to provide the required credentials, + will cause the handshake to fail, and therefore the connection to be aborted. + + \note The \a authenticator object is owned by the reply and must not be + deleted by the application. + + \sa QSslPreSharedKeyAuthenticator +*/ + /*! \fn void QNetworkReply::metaDataChanged() -- cgit v1.2.3