QSsl Namespace

The QSsl namespace declares enums common to all SSL classes in QtNetwork. More...

 #include <QSsl>

This namespace was introduced in Qt 4.3.

Types

enum AlternateNameEntryType { EmailEntry, DnsEntry }
enum EncodingFormat { Pem, Der }
enum KeyAlgorithm { Rsa, Dsa }
enum KeyType { PrivateKey, PublicKey }
enum SslOption { SslOptionDisableEmptyFragments, SslOptionDisableSessionTickets, SslOptionDisableCompression, SslOptionDisableServerNameIndication, SslOptionDisableLegacyRenegotiation }
flags SslOptions
enum SslProtocol { SslV3, SslV2, TlsV1, UnknownProtocol, ..., SecureProtocols }

Type Documentation

enum QSsl::AlternateNameEntryType

Describes the key types for alternate name entries in QSslCertificate.

ConstantValueDescription
QSsl::EmailEntry0An email entry; the entry contains an email address that the certificate is valid for.
QSsl::DnsEntry1A DNS host name entry; the entry contains a host name entry that the certificate is valid for. The entry may contain wildcards.

See also QSslCertificate::alternateSubjectNames().

enum QSsl::EncodingFormat

Describes supported encoding formats for certificates and keys.

ConstantValueDescription
QSsl::Pem0The PEM format.
QSsl::Der1The DER format.

enum QSsl::KeyAlgorithm

Describes the different key algorithms supported by QSslKey.

ConstantValueDescription
QSsl::Rsa0The RSA algorithm.
QSsl::Dsa1The DSA algorithm.

enum QSsl::KeyType

Describes the two types of keys QSslKey supports.

ConstantValueDescription
QSsl::PrivateKey0A private key.
QSsl::PublicKey1A public key.

enum QSsl::SslOption
flags QSsl::SslOptions

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.

ConstantValueDescription
QSsl::SslOptionDisableEmptyFragments0x01Disables 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.
QSsl::SslOptionDisableSessionTickets0x02Disables the SSL session ticket extension. This can cause slower connection setup, however some servers are not compatible with the extension.
QSsl::SslOptionDisableCompression0x04Disables 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.
QSsl::SslOptionDisableServerNameIndication0x08Disables 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.
QSsl::SslOptionDisableLegacyRenegotiation0x10Disables 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.

By default, SslOptionDisableEmptyFragments is turned on since this causes problems with a large number of servers. SslOptionDisableLegacyRenegotiation is also turned on, since it introduces a security risk. SslOptionDisableCompression is turned on to prevent the attack publicised by CRIME. The other options are turned off.

Note: Availability of above options depends on the version of the SSL backend in use.

The SslOptions type is a typedef for QFlags<SslOption>. It stores an OR combination of SslOption values.

enum QSsl::SslProtocol

Describes the protocol of the cipher.

ConstantValueDescription
QSsl::SslV30SSLv3
QSsl::SslV21SSLv2
QSsl::TlsV12TLSv1
QSsl::UnknownProtocol-1The cipher's protocol cannot be determined.
QSsl::AnyProtocol3The socket understands SSLv2, SSLv3, and TLSv1. This value is used by QSslSocket only.
QSsl::TlsV1SslV34On the client side, this will send a TLS 1.0 Client Hello, enabling TLSv1 and SSLv3 connections. On the server side, this will enable both SSLv3 and TLSv1 connections.
QSsl::SecureProtocols5The default option, using protocols known to be secure; currently behaves like TlsV1SslV3.

Note: most servers using SSL understand both versions (2 and 3), but it is recommended to use the latest version only for security reasons. However, SSL and TLS are not compatible with each other: if you get unexpected handshake failures, verify that you chose the correct setting for your protocol.

comments powered by Disqus