Skip to content

PythonQt.QtNetwork.QSslConfiguration · declarations 001

Back to PythonQt.QtNetwork.QSslConfiguration

NextProtocolNegotiationNegotiated instance-attribute

NextProtocolNegotiationNegotiated: Any

NextProtocolNegotiationNone instance-attribute

NextProtocolNegotiationNone: Any

NextProtocolNegotiationStatus instance-attribute

NextProtocolNegotiationStatus: type

int([x]) -> integer int(x, base=10) -> integer

Convert a number or string to an integer, or return 0 if no arguments are given. If x is a number, return x.int(). For floating point numbers, this truncates towards zero.

If x is not a number or if base is given, then x must be a string, bytes, or bytearray instance representing an integer literal in the given base. The literal can be preceded by '+' or '-' and be surrounded by whitespace. The base defaults to 10. Valid bases are 0 and 2-36. Base 0 means to interpret the base from the string as an integer literal.

int('0b100', base=0) 4

NextProtocolNegotiationUnsupported instance-attribute

NextProtocolNegotiationUnsupported: Any

allowedNextProtocols

allowedNextProtocols() -> Any

X.allowedNextProtocols()

Supplemental documentation: Qt 5 reference:

QList\<QByteArray> QSslConfiguration::allowedNextProtocols() const

This function returns the allowed protocols to be negotiated with the server through the Next Protocol Negotiation (NPN) or Application-Layer Protocol Negotiation (ALPN) TLS extension, as set by setAllowedNextProtocols().

This function was introduced in Qt 5.3.

See also nextNegotiatedProtocol(), nextProtocolNegotiationStatus(), setAllowedNextProtocols(), QSslConfiguration::NextProtocolSpdy3_0, and QSslConfiguration::NextProtocolHttp1_1.

Upstream PySide2 reference signatures (binding differences may apply):

allowedNextProtocols(self) -> typing.List[PySide2.QtCore.QByteArray]

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#allowedNextProtocols

caCertificates

caCertificates() -> tuple

X.caCertificates() -> tuple

Supplemental documentation: Qt 5 reference:

QList\<QSslCertificate> QSslConfiguration::caCertificates() const

Returns this connection's CA certificate database. The CA certificate database is used by the socket during the handshake phase to validate the peer's certificate. It can be modified prior to the handshake with setCaCertificates(), or with addCaCertificate() and addCaCertificates().

See also setCaCertificates(), addCaCertificate(), and addCaCertificates().

Upstream PySide2 reference signatures (binding differences may apply):

caCertificates(self) -> typing.List[PySide2.QtNetwork.QSslCertificate]

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#caCertificates

ciphers

ciphers() -> tuple

X.ciphers() -> tuple

Supplemental documentation: Qt 5 reference:

QList\<QSslCipher> QSslConfiguration::ciphers() const

Returns this connection's current cryptographic cipher suite. This list is used during the handshake phase for choosing a session cipher. The returned list of ciphers is ordered by descending preference. (i.e., the first cipher in the list is the most preferred cipher). The session cipher will be the first one in the list that is also supported by the peer.

By default, the handshake phase can choose any of the ciphers supported by this system's SSL libraries, which may vary from system to system. The list of ciphers supported by this system's SSL libraries is returned by QSslSocket::supportedCiphers(). You can restrict the list of ciphers used for choosing the session cipher for this socket by calling setCiphers() with a subset of the supported ciphers. You can revert to using the entire set by calling setCiphers() with the list returned by QSslSocket::supportedCiphers().

Note: This is not currently supported in the Schannel backend.

See also setCiphers() and QSslSocket::supportedCiphers().

Upstream PySide2 reference signatures (binding differences may apply):

ciphers(self) -> typing.List[PySide2.QtNetwork.QSslCipher]

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#ciphers

defaultConfiguration

defaultConfiguration() -> Any

X.defaultConfiguration() -> PythonQt.QtNetwork.QSslConfiguration

Supplemental documentation: Qt 5 reference:

[static] QSslConfiguration QSslConfiguration::defaultConfiguration()

Returns the default SSL configuration to be used in new SSL connections.

The default SSL configuration consists of:

  • no local certificate and no private key
  • protocol SecureProtocols
  • the system's default CA certificate list
  • the cipher list equal to the list of the SSL libraries' supported SSL ciphers that are 128 bits or more

See also QSslSocket::supportedCiphers() and setDefaultConfiguration().

Upstream PySide2 reference signatures (binding differences may apply):

defaultConfiguration() -> PySide2.QtNetwork.QSslConfiguration

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#defaultConfiguration

ellipticCurves

ellipticCurves() -> tuple

X.ellipticCurves() -> tuple

Supplemental documentation: Qt 5 reference:

QVector\<QSslEllipticCurve> QSslConfiguration::ellipticCurves() const

Returns this connection's current list of elliptic curves. This list is used during the handshake phase for choosing an elliptic curve (when using an elliptic curve cipher). The returned list of curves is ordered by descending preference (i.e., the first curve in the list is the most preferred one).

By default, the handshake phase can choose any of the curves supported by this system's SSL libraries, which may vary from system to system. The list of curves supported by this system's SSL libraries is returned by QSslSocket::supportedEllipticCurves().

You can restrict the list of curves used for choosing the session cipher for this socket by calling setEllipticCurves() with a subset of the supported ciphers. You can revert to using the entire set by calling setEllipticCurves() with the list returned by QSslSocket::supportedEllipticCurves().

This function was introduced in Qt 5.5.

See also setEllipticCurves.

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#ellipticCurves

isNull

isNull() -> bool

X.isNull() -> bool

Supplemental documentation: Qt 5 reference:

bool QSslConfiguration::isNull() const

Returns true if this is a null QSslConfiguration object.

A QSslConfiguration object is null if it has been default-constructed and no setter methods have been called.

See also setProtocol(), setLocalCertificate(), setPrivateKey(), setCiphers(), and setCaCertificates().

Upstream PySide2 reference signatures (binding differences may apply):

isNull(self) -> bool

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#isNull

localCertificate

localCertificate() -> Any

X.localCertificate() -> PythonQt.QtNetwork.QSslCertificate

Supplemental documentation: Qt 5 reference:

QSslCertificate QSslConfiguration::localCertificate() const

Returns the certificate to be presented to the peer during the SSL handshake process.

See also setLocalCertificate().

Upstream PySide2 reference signatures (binding differences may apply):

localCertificate(self) -> PySide2.QtNetwork.QSslCertificate

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#localCertificate

localCertificateChain

localCertificateChain() -> tuple

X.localCertificateChain() -> tuple

Supplemental documentation: Qt 5 reference:

QList\<QSslCertificate> QSslConfiguration::localCertificateChain() const

Returns the certificate chain to be presented to the peer during the SSL handshake process.

This function was introduced in Qt 5.1.

See also setLocalCertificateChain() and localCertificate().

Upstream PySide2 reference signatures (binding differences may apply):

localCertificateChain(self) -> typing.List[PySide2.QtNetwork.QSslCertificate]

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#localCertificateChain

nextNegotiatedProtocol

nextNegotiatedProtocol() -> Any

X.nextNegotiatedProtocol() -> PythonQt.QtCore.QByteArray

Supplemental documentation: Qt 5 reference:

QByteArray QSslConfiguration::nextNegotiatedProtocol() const

This function returns the protocol negotiated with the server if the Next Protocol Negotiation (NPN) or Application-Layer Protocol Negotiation (ALPN) TLS extension was enabled. In order for the NPN/ALPN extension to be enabled, setAllowedNextProtocols() needs to be called explicitly before connecting to the server.

If no protocol could be negotiated or the extension was not enabled, this function returns a QByteArray which is null.

This function was introduced in Qt 5.3.

See also setAllowedNextProtocols() and nextProtocolNegotiationStatus().

Upstream PySide2 reference signatures (binding differences may apply):

nextNegotiatedProtocol(self) -> PySide2.QtCore.QByteArray

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#nextNegotiatedProtocol

nextProtocolNegotiationStatus

nextProtocolNegotiationStatus() -> Any

X.nextProtocolNegotiationStatus()

Supplemental documentation: Qt 5 reference:

QSslConfiguration::NextProtocolNegotiationStatus QSslConfiguration::nextProtocolNegotiationStatus() const

This function returns the status of the Next Protocol Negotiation (NPN) or Application-Layer Protocol Negotiation (ALPN). If the feature has not been enabled through setAllowedNextProtocols(), this function returns NextProtocolNegotiationNone. The status will be set before emitting the encrypted() signal.

This function was introduced in Qt 5.3.

See also setAllowedNextProtocols(), allowedNextProtocols(), nextNegotiatedProtocol(), and QSslConfiguration::NextProtocolNegotiationStatus.

Upstream PySide2 reference signatures (binding differences may apply):

nextProtocolNegotiationStatus(self) -> PySide2.QtNetwork.QSslConfiguration.NextProtocolNegotiationStatus

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#nextProtocolNegotiationStatus

operator_assign

operator_assign(other: Any) -> Any

X.operator_assign(other) -> PythonQt.QtNetwork.QSslConfiguration

peerCertificate

peerCertificate() -> Any

X.peerCertificate() -> PythonQt.QtNetwork.QSslCertificate

Supplemental documentation: Qt 5 reference:

QSslCertificate QSslConfiguration::peerCertificate() const

Returns the peer's digital certificate (i.e., the immediate certificate of the host you are connected to), or a null certificate, if the peer has not assigned a certificate.

The peer certificate is checked automatically during the handshake phase, so this function is normally used to fetch the certificate for display or for connection diagnostic purposes. It contains information about the peer, including its host name, the certificate issuer, and the peer's public key.

Because the peer certificate is set during the handshake phase, it is safe to access the peer certificate from a slot connected to the QSslSocket::sslErrors() signal, QNetworkReply::sslErrors() signal, or the QSslSocket::encrypted() signal.

If a null certificate is returned, it can mean the SSL handshake failed, or it can mean the host you are connected to doesn't have a certificate, or it can mean there is no connection.

If you want to check the peer's complete chain of certificates, use peerCertificateChain() to get them all at once.

See also peerCertificateChain(), QSslSocket::sslErrors(), QSslSocket::ignoreSslErrors(), QNetworkReply::sslErrors(), and QNetworkReply::ignoreSslErrors().

Upstream PySide2 reference signatures (binding differences may apply):

peerCertificate(self) -> PySide2.QtNetwork.QSslCertificate

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#peerCertificate

peerCertificateChain

peerCertificateChain() -> tuple

X.peerCertificateChain() -> tuple

Supplemental documentation: Qt 5 reference:

QList\<QSslCertificate> QSslConfiguration::peerCertificateChain() const

Returns the peer's chain of digital certificates, starting with the peer's immediate certificate and ending with the CA's certificate.

Peer certificates are checked automatically during the handshake phase. This function is normally used to fetch certificates for display, or for performing connection diagnostics. Certificates contain information about the peer and the certificate issuers, including host name, issuer names, and issuer public keys.

Because the peer certificate is set during the handshake phase, it is safe to access the peer certificate from a slot connected to the QSslSocket::sslErrors() signal, QNetworkReply::sslErrors() signal, or the QSslSocket::encrypted() signal.

If an empty list is returned, it can mean the SSL handshake failed, or it can mean the host you are connected to doesn't have a certificate, or it can mean there is no connection.

If you want to get only the peer's immediate certificate, use peerCertificate().

See also peerCertificate(), QSslSocket::sslErrors(), QSslSocket::ignoreSslErrors(), QNetworkReply::sslErrors(), and QNetworkReply::ignoreSslErrors().

Upstream PySide2 reference signatures (binding differences may apply):

peerCertificateChain(self) -> typing.List[PySide2.QtNetwork.QSslCertificate]

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#peerCertificateChain

peerVerifyDepth

peerVerifyDepth() -> int

X.peerVerifyDepth() -> int

Supplemental documentation: Qt 5 reference:

int QSslConfiguration::peerVerifyDepth() const

Returns the maximum number of certificates in the peer's certificate chain to be checked during the SSL handshake phase, or 0 (the default) if no maximum depth has been set, indicating that the whole certificate chain should be checked.

The certificates are checked in issuing order, starting with the peer's own certificate, then its issuer's certificate, and so on.

See also setPeerVerifyDepth() and peerVerifyMode().

Upstream PySide2 reference signatures (binding differences may apply):

peerVerifyDepth(self) -> int

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#peerVerifyDepth

peerVerifyMode

peerVerifyMode() -> Any

X.peerVerifyMode()

Supplemental documentation: Qt 5 reference:

QSslSocket::PeerVerifyMode QSslConfiguration::peerVerifyMode() const

Returns the verify mode. This mode decides whether QSslSocket should request a certificate from the peer (i.e., the client requests a certificate from the server, or a server requesting a certificate from the client), and whether it should require that this certificate is valid.

The default mode is AutoVerifyPeer, which tells QSslSocket to use VerifyPeer for clients, QueryPeer for servers.

See also setPeerVerifyMode().

Upstream PySide2 reference signatures (binding differences may apply):

peerVerifyMode(self) -> PySide2.QtNetwork.QSslSocket.PeerVerifyMode

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#peerVerifyMode

privateKey

privateKey() -> Any

X.privateKey() -> PythonQt.QtNetwork.QSslKey

Supplemental documentation: Qt 5 reference:

QSslKey QSslConfiguration::privateKey() const

Returns the SSL key assigned to this connection or a null key if none has been assigned yet.

See also setPrivateKey() and localCertificate().

Upstream PySide2 reference signatures (binding differences may apply):

privateKey(self) -> PySide2.QtNetwork.QSslKey

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#privateKey

protocol

protocol() -> Any

X.protocol()

Supplemental documentation: Qt 5 reference:

QSsl::SslProtocol QSslConfiguration::protocol() const

Returns the protocol setting for this SSL configuration.

See also setProtocol().

Upstream PySide2 reference signatures (binding differences may apply):

protocol(self) -> PySide2.QtNetwork.QSsl.SslProtocol

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#protocol

sessionCipher

sessionCipher() -> Any

X.sessionCipher() -> PythonQt.QtNetwork.QSslCipher

Supplemental documentation: Qt 5 reference:

QSslCipher QSslConfiguration::sessionCipher() const

Returns the socket's cryptographic cipher, or a null cipher if the connection isn't encrypted. The socket's cipher for the session is set during the handshake phase. The cipher is used to encrypt and decrypt data transmitted through the socket.

The SSL infrastructure also provides functions for setting the ordered list of ciphers from which the handshake phase will eventually select the session cipher. This ordered list must be in place before the handshake phase begins.

See also ciphers(), setCiphers(), and QSslSocket::supportedCiphers().

Upstream PySide2 reference signatures (binding differences may apply):

sessionCipher(self) -> PySide2.QtNetwork.QSslCipher

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#sessionCipher

sessionProtocol

sessionProtocol() -> Any

X.sessionProtocol()

Supplemental documentation: Qt 5 reference:

QSsl::SslProtocol QSslConfiguration::sessionProtocol() const

Returns the socket's SSL/TLS protocol or UnknownProtocol if the connection isn't encrypted. The socket's protocol for the session is set during the handshake phase.

This function was introduced in Qt 5.4.

See also protocol() and setProtocol().

Upstream PySide2 reference signatures (binding differences may apply):

sessionProtocol(self) -> PySide2.QtNetwork.QSsl.SslProtocol

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#sessionProtocol

sessionTicket

sessionTicket() -> Any

X.sessionTicket() -> PythonQt.QtCore.QByteArray

Supplemental documentation: Qt 5 reference:

QByteArray QSslConfiguration::sessionTicket() const

If QSsl::SslOptionDisableSessionPersistence was turned off, this function returns the session ticket used in the SSL handshake in ASN.1 format, suitable to e.g. be persisted to disk. If no session ticket was used or QSsl::SslOptionDisableSessionPersistence was not turned off, this function returns an empty QByteArray.

Note: When persisting the session ticket to disk or similar, be careful not to expose the session to a potential attacker, as knowledge of the session allows for eavesdropping on data encrypted with the session parameters.

This function was introduced in Qt 5.2.

See also setSessionTicket(), QSsl::SslOptionDisableSessionPersistence, setSslOption(), and QSslSocket::newSessionTicketReceived().

Upstream PySide2 reference signatures (binding differences may apply):

sessionTicket(self) -> PySide2.QtCore.QByteArray

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#sessionTicket

sessionTicketLifeTimeHint

sessionTicketLifeTimeHint() -> int

X.sessionTicketLifeTimeHint() -> int

Supplemental documentation: Qt 5 reference:

int QSslConfiguration::sessionTicketLifeTimeHint() const

If QSsl::SslOptionDisableSessionPersistence was turned off, this function returns the session ticket life time hint sent by the server (which might be 0). If the server did not send a session ticket (e.g. when resuming a session or when the server does not support it) or QSsl::SslOptionDisableSessionPersistence was not turned off, this function returns -1.

This function was introduced in Qt 5.2.

See also sessionTicket(), QSsl::SslOptionDisableSessionPersistence, setSslOption(), and QSslSocket::newSessionTicketReceived().

Upstream PySide2 reference signatures (binding differences may apply):

sessionTicketLifeTimeHint(self) -> int

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#sessionTicketLifeTimeHint

setAllowedNextProtocols

setAllowedNextProtocols(protocols: Any) -> None

X.setAllowedNextProtocols(protocols)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setAllowedNextProtocols(QList\<QByteArray> protocols)

This function sets the allowed protocols to be negotiated with the server through the Next Protocol Negotiation (NPN) or Application-Layer Protocol Negotiation (ALPN) TLS extension; each element in protocols must define one allowed protocol. The function must be called explicitly before connecting to send the NPN/ALPN extension in the SSL handshake. Whether or not the negotiation succeeded can be queried through nextProtocolNegotiationStatus().

This function was introduced in Qt 5.3.

See also nextNegotiatedProtocol(), nextProtocolNegotiationStatus(), allowedNextProtocols(), QSslConfiguration::NextProtocolSpdy3_0, and QSslConfiguration::NextProtocolHttp1_1.

Upstream PySide2 reference signatures (binding differences may apply):

setAllowedNextProtocols(self, protocols: typing.Sequence[PySide2.QtCore.QByteArray]) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setAllowedNextProtocols

setCaCertificates

setCaCertificates(certificates: Any) -> None

X.setCaCertificates(certificates)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setCaCertificates(const QList\<QSslCertificate> \&certificates)

Sets this socket's CA certificate database to be certificates. The certificate database must be set prior to the SSL handshake. The CA certificate database is used by the socket during the handshake phase to validate the peer's certificate.

Note: The default configuration uses the system CA certificate database. If that is not available (as is commonly the case on iOS), the default database is empty.

See also caCertificates(), addCaCertificates(), and addCaCertificate().

Upstream PySide2 reference signatures (binding differences may apply):

setCaCertificates(self, certificates: typing.Sequence[PySide2.QtNetwork.QSslCertificate]) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setCaCertificates

setCiphers

setCiphers(ciphers: Any) -> None

X.setCiphers(ciphers)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setCiphers(const QList\<QSslCipher> \&ciphers)

Sets the cryptographic cipher suite for this socket to ciphers, which must contain a subset of the ciphers in the list returned by supportedCiphers().

Restricting the cipher suite must be done before the handshake phase, where the session cipher is chosen.

Note: This is not currently supported in the Schannel backend.

See also ciphers() and QSslSocket::supportedCiphers().

Upstream PySide2 reference signatures (binding differences may apply):

setCiphers(self, ciphers: typing.Sequence[PySide2.QtNetwork.QSslCipher]) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setCiphers

setDefaultConfiguration

setDefaultConfiguration(configuration: Any) -> None

X.setDefaultConfiguration(configuration)

Supplemental documentation: Qt 5 reference:

[static] void QSslConfiguration::setDefaultConfiguration(const QSslConfiguration \&configuration)

Sets the default SSL configuration to be used in new SSL connections to be configuration. Existing connections are not affected by this call.

See also QSslSocket::supportedCiphers() and defaultConfiguration().

Upstream PySide2 reference signatures (binding differences may apply):

setDefaultConfiguration(configuration: PySide2.QtNetwork.QSslConfiguration) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setDefaultConfiguration

setEllipticCurves

setEllipticCurves(curves: Any) -> Any

X.setEllipticCurves(curves)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setEllipticCurves(const QVector\<QSslEllipticCurve> \&curves)

Sets the list of elliptic curves to be used by this socket to curves, which must contain a subset of the curves in the list returned by supportedEllipticCurves().

Restricting the elliptic curves must be done before the handshake phase, where the session cipher is chosen.

This function was introduced in Qt 5.5.

See also ellipticCurves.

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setEllipticCurves

setLocalCertificate

setLocalCertificate(certificate: Any) -> None

X.setLocalCertificate(certificate)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setLocalCertificate(const QSslCertificate \&certificate)

Sets the certificate to be presented to the peer during SSL handshake to be certificate.

Setting the certificate once the connection has been established has no effect.

A certificate is the means of identification used in the SSL process. The local certificate is used by the remote end to verify the local user's identity against its list of Certification Authorities. In most cases, such as in HTTP web browsing, only servers identify to the clients, so the client does not send a certificate.

See also localCertificate().

Upstream PySide2 reference signatures (binding differences may apply):

setLocalCertificate(self, certificate: PySide2.QtNetwork.QSslCertificate) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setLocalCertificate

setLocalCertificateChain

setLocalCertificateChain(localChain: Any) -> None

X.setLocalCertificateChain(localChain)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setLocalCertificateChain(const QList\<QSslCertificate> \&localChain)

Sets the certificate chain to be presented to the peer during the SSL handshake to be localChain.

Setting the certificate chain once the connection has been established has no effect.

A certificate is the means of identification used in the SSL process. The local certificate is used by the remote end to verify the local user's identity against its list of Certification Authorities. In most cases, such as in HTTP web browsing, only servers identify to the clients, so the client does not send a certificate.

Unlike QSslConfiguration::setLocalCertificate() this method allows you to specify any intermediate certificates required in order to validate your certificate. The first item in the list must be the leaf certificate.

This function was introduced in Qt 5.1.

See also localCertificateChain().

Upstream PySide2 reference signatures (binding differences may apply):

setLocalCertificateChain(self, localChain: typing.Sequence[PySide2.QtNetwork.QSslCertificate]) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setLocalCertificateChain

setPeerVerifyDepth

setPeerVerifyDepth(depth: int) -> None

X.setPeerVerifyDepth(depth)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setPeerVerifyDepth(int depth)

Sets the maximum number of certificates in the peer's certificate chain to be checked during the SSL handshake phase, to depth. Setting a depth of 0 means that no maximum depth is set, indicating that the whole certificate chain should be checked.

The certificates are checked in issuing order, starting with the peer's own certificate, then its issuer's certificate, and so on.

See also peerVerifyDepth() and setPeerVerifyMode().

Upstream PySide2 reference signatures (binding differences may apply):

setPeerVerifyDepth(self, depth: int) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setPeerVerifyDepth

setPeerVerifyMode

setPeerVerifyMode(mode: Any) -> None

X.setPeerVerifyMode(mode)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setPeerVerifyMode(QSslSocket::PeerVerifyMode mode)

Sets the verify mode to mode. This mode decides whether QSslSocket should request a certificate from the peer (i.e., the client requests a certificate from the server, or a server requesting a certificate from the client), and whether it should require that this certificate is valid.

The default mode is AutoVerifyPeer, which tells QSslSocket to use VerifyPeer for clients, QueryPeer for servers.

See also peerVerifyMode().

Upstream PySide2 reference signatures (binding differences may apply):

setPeerVerifyMode(self, mode: PySide2.QtNetwork.QSslSocket.PeerVerifyMode) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setPeerVerifyMode

setPrivateKey

setPrivateKey(key: Any) -> None

X.setPrivateKey(key)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setPrivateKey(const QSslKey \&key)

Sets the connection's private key to key. The private key and the local certificate are used by clients and servers that must prove their identity to SSL peers.

Both the key and the local certificate are required if you are creating an SSL server socket. If you are creating an SSL client socket, the key and local certificate are required if your client must identify itself to an SSL server.

See also privateKey() and setLocalCertificate().

Upstream PySide2 reference signatures (binding differences may apply):

setPrivateKey(self, key: PySide2.QtNetwork.QSslKey) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setPrivateKey

setProtocol

setProtocol(protocol: Any) -> None

X.setProtocol(protocol)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setProtocol(QSsl::SslProtocol protocol)

Sets the protocol setting for this configuration to be protocol.

Setting the protocol once the connection has already been established has no effect.

See also protocol().

Upstream PySide2 reference signatures (binding differences may apply):

setProtocol(self, protocol: PySide2.QtNetwork.QSsl.SslProtocol) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setProtocol

setSessionTicket

setSessionTicket(sessionTicket: Any) -> None

X.setSessionTicket(sessionTicket)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setSessionTicket(const QByteArray \&sessionTicket)

Sets the session ticket to be used in an SSL handshake. QSsl::SslOptionDisableSessionPersistence must be turned off for this to work, and sessionTicket must be in ASN.1 format as returned by sessionTicket().

This function was introduced in Qt 5.2.

See also sessionTicket(), QSsl::SslOptionDisableSessionPersistence, setSslOption(), and QSslSocket::newSessionTicketReceived().

Upstream PySide2 reference signatures (binding differences may apply):

setSessionTicket(self, sessionTicket: PySide2.QtCore.QByteArray) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setSessionTicket

setSslOption

setSslOption(option: Any, on: bool) -> None

X.setSslOption(option, on)

Supplemental documentation: Qt 5 reference:

void QSslConfiguration::setSslOption(QSsl::SslOption option, bool on)

Enables or disables an SSL compatibility option. If on is true, the option is enabled. If on is false, the option is disabled.

See also testSslOption().

Upstream PySide2 reference signatures (binding differences may apply):

setSslOption(self, option: PySide2.QtNetwork.QSsl.SslOption, on: bool) -> None

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#setSslOption

supportedCiphers

supportedCiphers() -> tuple

X.supportedCiphers() -> tuple

Supplemental documentation: Qt 5 reference:

[static] QList\<QSslCipher> QSslConfiguration::supportedCiphers()

Returns the list of cryptographic ciphers supported by this system. This list is set by the system's SSL libraries and may vary from system to system.

This function was introduced in Qt 5.5.

See also ciphers() and setCiphers().

Upstream PySide2 reference signatures (binding differences may apply):

supportedCiphers() -> typing.List[PySide2.QtNetwork.QSslCipher]

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#supportedCiphers

supportedEllipticCurves

supportedEllipticCurves() -> tuple

X.supportedEllipticCurves() -> tuple

Supplemental documentation: Qt 5 reference:

[static] QVector\<QSslEllipticCurve> QSslConfiguration::supportedEllipticCurves()

Returns the list of elliptic curves supported by this system. This list is set by the system's SSL libraries and may vary from system to system.

This function was introduced in Qt 5.5.

See also ellipticCurves() and setEllipticCurves().

Source: https://doc.qt.io/archives/qt-5.15/qsslconfiguration.html#supportedEllipticCurves