The QSsl namespace declares enums common to all SSL classes in Qt Network. More…
Describes the two types of keys
A private key.
A public key.
Describes supported encoding formats for certificates and keys.
The PEM format.
The DER format.
Describes the different key algorithms supported by
The RSA algorithm.
The DSA algorithm.
The Elliptic Curve algorithm.
The Diffie-Hellman algorithm.
A key that should be treated as a ‘black box’ by
The opaque key facility allows applications to add support for facilities such as PKCS#11 that Qt does not currently offer natively.
Describes the key types for alternative name entries in
An email entry; the entry contains an email address that the certificate is valid for.
A DNS host name entry; the entry contains a host name entry that the certificate is valid for. The entry may contain wildcards.
An IP address entry; the entry contains an IP address entry that the certificate is valid for, introduced in Qt 5.13.
Describes the protocol of the cipher.
TLSv1.0 and later versions.
TLSv1.1 and later versions.
TLSv1.2 and later versions.
DTLSv1.0 and later versions.
DTLSv1.2 and later versions.
TLSv1.3. (Since Qt 5.12)
TLSv1.3 and later versions. (Since Qt 5.12)
The cipher’s protocol cannot be determined.
Any supported protocol. This value is used by
The default option, using protocols known to be secure.
Describes the options that can be used to control the details of SSL behaviour. These options are generally used to turn features off to work around buggy servers.
Disables the insertion of empty fragments into the data when using block ciphers. When enabled, this prevents some attacks (such as the BEAST attack), however it is incompatible with some servers.
Disables the SSL session ticket extension. This can cause slower connection setup, however some servers are not compatible with the extension.
Disables the SSL compression extension. When enabled, this allows the data being passed over SSL to be compressed, however some servers are not compatible with this extension.
Disables the SSL server name indication extension. When enabled, this tells the server the virtual host being accessed allowing it to respond with the correct certificate.
Disables the older insecure mechanism for renegotiating the connection parameters. When enabled, this option can allow connections for legacy servers, but it introduces the possibility that an attacker could inject plaintext into the SSL session.
Disables SSL session sharing via the session ID handshake attribute.
Disables storing the SSL session in ASN.1 format as returned by
sessionTicket(). Enabling this feature adds memory overhead of approximately 1K per used session ticket.
Disables selecting the cipher chosen based on the servers preferences rather than the order ciphers were sent by the client. This option is only relevant to server sockets, and is only honored by the OpenSSL backend.
By default, is turned on since this causes problems with a large number of servers. is also turned on, since it introduces a security risk. is turned on to prevent the attack publicised by CRIME. is turned on to optimize memory usage. The other options are turned off.
Availability of above options depends on the version of the SSL backend in use.
Describes the level of an alert message
This enum describes the level of an alert message that was sent or received.
Non-fatal alert message
Fatal alert message, the underlying backend will handle such an alert properly and close the connection.
An alert of unknown level of severity.
New in version 6.0.
Enumerates possible codes that an alert message can have
See RFC 8446, section 6 for the possible values and their meaning.
New in version 6.0.
© 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.