Secure Sockets Layer (SSL) Classes¶
Classes for secure communication over network sockets.
The classes below provide support for secure network communication using the Secure Sockets Layer (SSL) protocol, using the OpenSSL Toolkit to perform encryption and protocol handling.
From Qt version 5.6 onwards, the officially supported version for OpenSSL is 1.0.0 or later.
This class implements server-side DTLS cookie generation and verification.
This class defines parameters for DTLS cookie generator.
Describes errors that can be found by QDtls and QDtlsClientVerifier.
This class provides encryption for UDP sockets.
Describes the current state of DTLS handshake.
This class represents Online Certificate Status Protocol response.
Describes the Online Certificate Status
Describes the reason for revocation
The QSsl namespace declares enums common to all SSL classes in Qt Network.
Describes the level of an alert message
Enumerates possible codes that an alert message can have
Enumerates classes that a TLS backend implements
Enumerates possible features that a TLS backend supports
The QSslCertificate class provides a convenient API for an X509 certificate.
The QSslCertificateExtension class provides an API for accessing the extensions of an X509 certificate.
The QSslCipher class represents an SSL cryptographic cipher.
The QSslConfiguration class holds the configuration and state of an SSL connection.
The QSslDiffieHellmanParameters class provides an interface for Diffie-Hellman parameters for servers.
Represents an elliptic curve for use by elliptic-curve cipher algorithms.
The QSslError class provides an SSL error.
The QSslKey class provides an interface for private and public keys.
The QSslPreSharedKeyAuthenticator class provides authentication data for pre shared keys (PSK) ciphersuites.
The QSslSocket class provides an SSL encrypted socket for both clients and servers.
Enabling and Disabling SSL Support¶
When building Qt from source, the configuration system checks for the presence of the
openssl/opensslv.h header provided by source or developer packages of OpenSSL.
By default, an SSL-enabled Qt library dynamically loads any installed OpenSSL library at run-time. However, it is possible to link against the library at compile-time by configuring Qt with the
When building a version of Qt linked against OpenSSL, Qt’s build system will use CMake’s
FindOpenSSL command to find OpenSSL in several standard locations. You can set the CMake variable OPENSSL_ROOT_DIR to force a specific location.
configure -openssl-linked -- -D OPENSSL_ROOT_DIR=<openssl_dir>
To disable SSL support in a Qt build, configure Qt with the
Datagram Transport Layer Security¶
Datagram Transport Layer Security (DTLS) is a protocol that enables security for datagram-based applications, providing them with protection against eavesdropping, tampering, or message forgery. The DTLS protocol is based on the stream-oriented Transport Layer Security (TLS) protocol. QtNetwork enables the use of DTLS with User Datagram Protocol (UDP), as defined by RFC 6347 .
Import and Export Restrictions¶
Qt binary installers include the OpenSSL libraries used by QtNetwork . However, those are not automatically deployed with applications that are built with Qt. Import and export restrictions apply for some types of software, and for some parts of the world. Developers wishing to use SSL communication in their deployed applications should either ensure that their users have the appropriate libraries installed, or they should consult a suitably qualified legal professional to ensure that applications using code from the OpenSSL project are correctly certified for import and export in relevant regions of the world.
© 2021 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.