/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:9:
  Home · All Classes · Modules

QSslSocket Class Reference
[QtNetwork module]

The QSslSocket class provides an SSL encrypted socket for both clients and servers. More...

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:10:

Inherits QTcpSocket.

Types

Methods

Static Methods

Qt Signals


Detailed Description

The QSslSocket class provides an SSL encrypted socket for both clients and servers.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:11:

QSslSocket establishes a secure, encrypted TCP connection you can use for transmitting encrypted data. It can operate in both client and server mode, and it supports modern SSL protocols, including SSLv3 and TLSv1. By default, QSslSocket uses SSLv3, but you can change the SSL protocol by calling setProtocol() as long as you do it before the handshake has started.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:12:

SSL encryption operates on top of the existing TCP stream after the socket enters the ConnectedState. There are two simple ways to establish a secure connection using QSslSocket: With an immediate SSL handshake, or with a delayed SSL handshake occurring after the connection has been established in unencrypted mode.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:13:

The most common way to use QSslSocket is to construct an object and start a secure connection by calling connectToHostEncrypted(). This method starts an immediate SSL handshake once the connection has been established.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:20:

An example of using the delayed SSL handshake to secure an existing connection is the case where an SSL server secures an incoming connection. Suppose you create an SSL server class as a subclass of QTcpServer. You would override QTcpServer.incomingConnection() with something like the example below, which first constructs an instance of QSslSocket and then calls setSocketDescriptor() to set the new socket's descriptor to the existing one passed in. It then initiates the SSL handshake by calling startServerEncryption().

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:31:

If an error occurs, QSslSocket emits the sslErrors() signal. In this case, if no action is taken to ignore the error(s), the connection is dropped. To continue, despite the occurrence of an error, you can call ignoreSslErrors(), either from within this slot after the error occurs, or any time after construction of the QSslSocket and before the connection is attempted. This will allow QSslSocket to ignore the errors it encounters when establishing the identity of the peer. Ignoring errors during an SSL handshake should be used with caution, since a fundamental characteristic of secure connections is that they should be established with a successful handshake.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:32:

Once encrypted, you use QSslSocket as a regular QTcpSocket. When readyRead() is emitted, you can call read(), canReadLine() and readLine(), or getChar() to read decrypted data from QSslSocket's internal buffer, and you can call write() or putChar() to write data back to the peer. QSslSocket will automatically encrypt the written data for you, and emit bytesWritten() once the data has been written to the peer.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:52:

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:58:QSslSocket.QueryPeer1QSslSocket will request a certificate from the peer, but does not require this certificate to be valid. This is useful when you want to display peer certificate details to the user without affecting the actual SSL handshake. This mode is the default for servers. /PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:59:QSslSocket.VerifyPeer2QSslSocket will request a certificate from the peer during the SSL handshake phase, and requires that this certificate is valid. On failure, QSslSocket will emit the QSslSocket.sslErrors() signal. This mode is the default for clients. /PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:68:QSslSocket.SslClientMode1The socket is a client-side SSL socket. It is either alreayd encrypted, or it is in the SSL handshake phase (see QSslSocket.isEncrypted()). /PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:69:QSslSocket.SslServerMode2The socket is a server-side SSL socket. It is either already encrypted, or it is in the SSL handshake phase (see QSslSocket.isEncrypted()). /PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:85:

QSslSocket.addDefaultCaCertificate (QSslCertificate certificate)

Adds certificate to the default CA certificate database. Each SSL socket's CA certificate database is initialized to the default CA certificate database.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:88:

Each SSL socket's CA certificate database is initialized to the default CA certificate database.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:91:

Adds certificates to the default CA certificate database. Each SSL socket's CA certificate database is initialized to the default CA certificate database.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:96:

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 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 supportedCiphers().

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:100:

QSslSocket first enters the HostLookupState. Then, after entering either the event loop or one of the waitFor...() functions, it enters the ConnectingState, emits connected(), and then initiates the SSL client handshake. At each state change, QSslSocket emits signal stateChanged().

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:101:

After initiating the SSL client handshake, if the identity of the peer can't be established, signal sslErrors() is emitted. If you want to ignore the errors and continue connecting, you must call ignoreSslErrors(), either from inside a slot function connected to the sslErrors() signal, or prior to entering encrypted mode. If ignoreSslErrors is not called, the connection is dropped, signal disconnected() is emitted, and QSslSocket returns to the UnconnectedState.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:102:

If the SSL handshake is successful, QSslSocket emits encrypted().

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:113:

Each SSL socket's CA certificate database is initialized to the default CA certificate database.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:116:

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 supportedCiphers().

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:126:

If there are no errors during the SSL handshake phase (i.e., the identity of the peer is established with no problems), QSslSocket will not emit the sslErrors() signal, and it is unnecessary to call this function.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:127:

Ignoring errors that occur during an SSL handshake should be done with caution. A fundamental characteristic of secure connections is that they should be established with an error free handshake.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:132:

You can call sessionCipher() to find which cryptographic cipher is used to encrypt and decrypt your data.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:142:

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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:148:

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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:151:

int QSslSocket.peerVerifyDepth (self)

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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:161:

QSsl.SslProtocol QSslSocket.protocol (self)

Returns the socket's SSL protocol. By default, QSsl.SslV3 is used.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:167:

object QSslSocket.readData (self, long maxlen)

QSslCipher QSslSocket.sessionCipher (self)

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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:170:

QSslSocket.setCaCertificates (self, 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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:179: socket.setCiphers("DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA"); /PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:183:

Each SSL socket's CA certificate database is initialized to the default CA certificate database.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:186:

Restricting the default cipher suite only affects SSL sockets that perform their handshake phase after the default cipher suite has been changed.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:193:

QSslSocket.setPeerVerifyDepth (self, 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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:202:

QSslSocket.setPrivateKey (self, QSslKey key)

Sets the socket'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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:203:

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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:205:

QSslSocket.setPrivateKey (self, QString fileName, QSsl.KeyAlgorithm algorithm = QSsl.Rsa, QSsl.EncodingFormat format = QSsl.Pem, QByteArray passPhrase = QByteArray())

This is an overloaded member function, provided for convenience.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:206:

Reads the string in file fileName and decodes it using a specified algorithm and encoding format to construct an SSL key. If the encoded key is encrypted, passPhrase is used to decrypt it.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:207:

The socket's private key is set to the constructed key. The private key and the local certificate are used by clients and servers that must prove their identity to SSL peers.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:208:

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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:210:

QSslSocket.setProtocol (self, QSsl.SslProtocol protocol)

Sets the socket's SSL protocol to protocol. This will affect the next initiated handshake; calling this function on an already-encrypted socket will not affect the socket's protocol.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:217:

QSslSocket.setSslConfiguration (self, QSslConfiguration config)

Sets the socket's SSL configuration to be the contents of configuration. This function sets the local certificate, the ciphers, the private key and the CA certificates to those stored in configuration.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:218:

It is not possible to set the SSL-state related fields.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:221:

QSslConfiguration QSslSocket.sslConfiguration (self)

Returns the socket's SSL configuration state. The default SSL configuration of a socket is to use the default ciphers, default CA certificates, no local private key or certificate.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:222:

The SSL configuration also contains fields that can change with time without notice.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:225:

QList<QSslError> QSslSocket.sslErrors (self)

Returns a list of the last SSL errors that occurred. This is the same list as QSslSocket passes via the sslErrors() signal. If the connection has been encrypted with no errors, this function will return an empty list.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:228:

Clients that implement STARTTLS functionality often make use of delayed SSL handshakes. Most other clients can avoid calling this function directly by using connectToHostEncrypted() instead, which automatically performs the handshake.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:231:

For server sockets, calling this function is the only way to initiate the SSL handshake. Most servers will call this function immediately upon receiving a connection, or as a result of having received a protocol-specific command to enter SSL mode (e.g, the server may respond to receiving the string "STARTTLS\r\n" by calling this function).

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:232:

The most common way to implement an SSL server is to create a subclass of QTcpServer and reimplement QTcpServer.incomingConnection(). The returned socket descriptor is then passed to QSslSocket.setSocketDescriptor().

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:234:

QList<QSslCipher> QSslSocket.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.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:236:

bool QSslSocket.supportsSsl ()

Returns true if this platform supports SSL; otherwise, returns false. If the platform doesn't support SSL, the socket will fail in the connection phase.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:243:

bool QSslSocket.waitForEncrypted (self, int msecs = 30000)

Waits until the socket has completed the SSL handshake and has emitted encrypted(), or msecs milliseconds, whichever comes first. If encrypted() has been emitted, this function returns true; otherwise (e.g., the socket is disconnected, or the SSL handshake fails), false is returned.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:257:

void peerVerifyError (const QSslError&)

QSslSocket can emit this signal several times during the SSL handshake, before encryption has been established, to indicate that an error has occurred while establishing the identity of the peer. The error is usually an indication that QSslSocket is unable to securely identify the peer.

/PyQt-x11-gpl-4.4.4/doc/html/qsslsocket.html:262:

QSslSocket emits this signal after the SSL handshake to indicate that one or more errors have occurred while establishing the identity of the peer. The errors are usually an indication that QSslSocket is unable to securely identify the peer. Unless any action is taken, the connection will be dropped after this signal has been emitted.

/PyQt-x11-gpl-4.4.4/doc/html/qsslkey.html:15:

QSslKey.__init__ (self, QByteArray encoded, QSsl.KeyAlgorithm algorithm, QSsl.EncodingFormat format = QSsl.Pem, QSsl.KeyType type = QSsl.PrivateKey, QByteArray passPhrase = QByteArray())

Constructs a QSslKey by decoding the string in the byte array encoded using a specified algorithm and encoding format. If the encoded key is encrypted, passPhrase is used to decrypt it. type specifies whether the key is public or private.

/PyQt-x11-gpl-4.4.4/doc/html/qsslkey.html:17:

QSslKey.__init__ (self, QIODevice device, QSsl.KeyAlgorithm algorithm, QSsl.EncodingFormat format = QSsl.Pem, QSsl.KeyType type = QSsl.PrivateKey, QByteArray passPhrase = QByteArray())

Constructs a QSslKey by reading and decoding data from a device using a specified algorithm and encoding format. If the encoded key is encrypted, passPhrase is used to decrypt it. type specifies whether the key is public or private.

/PyQt-x11-gpl-4.4.4/doc/html/qscriptengine.html:10:

Inherits QObject.

Types

Methods

Qt Signals


Detailed Description

The QScriptEngine class provides an environment for evaluating Qt Script code.

/PyQt-x11-gpl-4.4.4/doc/html/qscriptengine.html:77:

Use newFunction() to wrap native (C++) functions, including constructors for your own custom types, so that these can be invoked from script code. Such functions must have the signature QScriptEngine.FunctionSignature. You may then pass the function as argument to newFunction(). Here is an example of a function that returns the sum of its first two arguments:

/PyQt-x11-gpl-4.4.4/doc/html/qscriptengine.html:187:

QScriptValue QScriptEngine.newFunction (self, callable signature, int length = 0)

Creates a QScriptValue that wraps a native (C++) function. fun must be a C++ function with signature QScriptEngine.FunctionSignature. length is the number of arguments that fun expects; this becomes the length property of the created QScriptValue.

/PyQt-x11-gpl-4.4.4/doc/html/qscriptengine.html:210:

QScriptValue QScriptEngine.newFunction (self, callable signature, QScriptValue prototype, int length = 0)

This is an overloaded member function, provided for convenience.

/PyQt-x11-gpl-4.4.4/doc/html/qhostinfo.html:12:

To look up a host's IP addresses asynchronously, call lookupHost(), which takes the host name or IP address, a receiver object, and a slot signature as arguments and returns an ID. You can abort the lookup by calling abortHostLookup() with the lookup ID.

/PyQt-x11-gpl-4.4.4/doc/html/qnetworkaccessmanager.html:83:

void sslErrors (QNetworkReply *,const QList<QSslError>&)

This signal is emitted if the SSL/TLS session encountered errors during the set up, including certificate verification errors. The errors parameter contains the list of errors and reply is the QNetworkReply that is encountering these errors.

/PyQt-x11-gpl-4.4.4/doc/html/qnetworkaccessmanager.html:84:

To indicate that the errors are not fatal and that the connection should proceed, the QNetworkReply.ignoreSslErrors() function should be called from the slot connected to this signal. If it is not called, the SSL session will be torn down before any data is exchanged (including the URL).

/PyQt-x11-gpl-4.4.4/doc/html/qnetworkaccessmanager.html:85:

This signal can be used to display an error message to the user indicating that security may be compromised and display the SSL settings (see sslConfiguration() to obtain it). If the user decides to proceed after analyzing the remote certificate, the slot should call ignoreSslErrors().

/PyQt-x11-gpl-4.4.4/doc/html/qsqldatabase.html:203:
  • CLIENT_SSL
  • /PyQt-x11-gpl-4.4.4/doc/html/qsqldatabase.html:240: db.setConnectOptions("CLIENT_SSL=1;CLIENT_IGNORE_SPACE=1"); // use an SSL connection to the server /PyQt-x11-gpl-4.4.4/doc/html/qsqldatabase.html:247: db.setConnectOptions("requiressl=1"); // enable PostgreSQL SSL connections /PyQt-x11-gpl-4.4.4/doc/html/qcryptographichash.html:10:

    Types

    Methods

    Static Methods


    Detailed Description

    The QCryptographicHash class provides a way to generate cryptographic hashes.

    /PyQt-x11-gpl-4.4.4/doc/html/qcryptographichash.html:12:

    Currently MD4, MD5, and SHA1 are supported.

    /PyQt-x11-gpl-4.4.4/doc/html/qcryptographichash.html:15:QCryptographicHash.Md40Generate an MD4 hash sum /PyQt-x11-gpl-4.4.4/doc/html/qcryptographichash.html:16:QCryptographicHash.Md51Generate an MD5 hash sum /PyQt-x11-gpl-4.4.4/doc/html/qcryptographichash.html:17:QCryptographicHash.Sha12Generate an SHA1 hash sum /PyQt-x11-gpl-4.4.4/doc/html/qtcore.html:9:
      Home · All Classes · Modules

    QtCore Module

    The QtCore module contains core non-GUI functionality. More...

    Types

    Module Functions

    Module Members


    Detailed Description

    The QtCore module contains non-GUI functionality.

    /PyQt-x11-gpl-4.4.4/doc/html/qtcore.html:88:

    object pyqtSignature (str signature, str result = None)

    object Q_ARG (str type, object data)

    object Q_ENUMS (...)

    object Q_FLAGS (...)

    object Q_RETURN_ARG (str type)

    float qAbs (float t)

    Returns the absolute value of value. For example:

    /PyQt-x11-gpl-4.4.4/doc/html/qwebpage.html:220:
  • %Security% expands to U if SSL is enabled, otherwise N. SSL is enabled if QSslSocket.supportsSsl() returns true.
  • /PyQt-x11-gpl-4.4.4/doc/html/qsslcertificate.html:10:

    Types

    Methods

    Static Methods

    Special Methods


    Detailed Description

    The QSslCertificate class provides a convenient API for an X509 certificate.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslcertificate.html:35:

    QByteArray QSslCertificate.digest (self, QCryptographicHash.Algorithm algorithm = QCryptographicHash.Md5)

    Returns a cryptographic digest of this certificate. By default, and MD5 digest will be generated, but you can also specify a custom algorithm.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslcertificate.html:46:
     foreach (QSslCertificate cert, QSslCertificate.fromPath("C:/ssl/certificate.*.pem",
    Binární soubor /home/mitr/hash/grep-many/source/PyQt-x11-gpl-4.4.4/doc/html/images/qpen-bevel.png odpovídá
    Binární soubor /home/mitr/hash/grep-many/source/PyQt-x11-gpl-4.4.4/doc/html/images/containerextension-example.png odpovídá
    Binární soubor /home/mitr/hash/grep-many/source/PyQt-x11-gpl-4.4.4/doc/html/images/qpen-demo.png odpovídá
    Binární soubor /home/mitr/hash/grep-many/source/PyQt-x11-gpl-4.4.4/doc/html/images/parent-child-widgets.png odpovídá
    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:9:
      Home · All Classes · Modules

    QSslConfiguration Class Reference
    [QtNetwork module]

    The QSslConfiguration class holds the configuration and state of an SSL connection More...

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:10:

    Methods

    Static Methods

    Special Methods


    Detailed Description

    The QSslConfiguration class holds the configuration and state of an SSL connection

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:11:

    QSslConfiguration is used by Qt networking classes to relay information about an open SSL connection and to allow the application to control certain features of that connection.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:14:
  • The SSL/TLS protocol to be used
  • /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:23:
  • The cipher used to encrypt this session
  • /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:25:

    The state can only be obtained once the SSL connection starts, but not necessarily before it's done. Some settings may change during the course of the SSL connection without need to restart it (for instance, the cipher can be changed over time).

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:28:

    Note that changing settings in QSslConfiguration is not enough to change the settings in the related SSL connection. You must call setSslConfiguration on a modified QSslConfiguration object to achieve that. The following example illustrates how to change the protocol to TLSv1 in a QSslSocket object:

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:34:

    Method Documentation

    QSslConfiguration.__init__ (self)

    Constructs an empty SSL configuration. This configuration contains no valid settings and the state will be empty. isNull() will return true after this constructor is called.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:40:

    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().

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:42:

    QSslConfiguration QSslConfiguration.defaultConfiguration ()

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

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:43:

    The default SSL configuration consists of:

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:48:
  • the cipher list equal to the list of the SSL libraries' supported SSL ciphers
  • /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:54:

    QSslCertificate QSslConfiguration.localCertificate (self)

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

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:59:

    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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:65:

    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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:68:

    int QSslConfiguration.peerVerifyDepth (self)

    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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:74:

    QSslKey QSslConfiguration.privateKey (self)

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

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:76:

    QSsl.SslProtocol QSslConfiguration.protocol (self)

    Returns the protocol setting for this SSL configuration.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:78:

    QSslCipher QSslConfiguration.sessionCipher (self)

    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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:79:

    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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:81:

    QSslConfiguration.setCaCertificates (self, 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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:86:

    QSslConfiguration.setDefaultConfiguration (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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:88:

    QSslConfiguration.setLocalCertificate (self, QSslCertificate certificate)

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

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:90:

    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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:92:

    QSslConfiguration.setPeerVerifyDepth (self, 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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:98:

    QSslConfiguration.setPrivateKey (self, 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.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslconfiguration.html:99:

    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.

    /PyQt-x11-gpl-4.4.4/doc/html/qmetamethod.html:10:

    Types

    Methods


    Detailed Description

    The QMetaMethod class provides meta-data about a member function.

    /PyQt-x11-gpl-4.4.4/doc/html/qmetamethod.html:11:

    A QMetaMethod has a methodType(), a signature(), a list of parameterTypes() and parameterNames(), a return typeName(), a tag(), and an access() specifier.

    /PyQt-x11-gpl-4.4.4/doc/html/qmetamethod.html:32:

    See also parameterTypes() and signature().

    /PyQt-x11-gpl-4.4.4/doc/html/qmetamethod.html:34:

    See also parameterNames() and signature().

    /PyQt-x11-gpl-4.4.4/doc/html/qmetamethod.html:35:

    str QMetaMethod.signature (self)

    Returns the signature of this method (e.g., setValue(double)).

    /PyQt-x11-gpl-4.4.4/doc/html/qnetworkrequest.html:71:

    QNetworkRequest.setSslConfiguration (self, QSslConfiguration configuration)

    Sets this network request's SSL configuration to be config. The settings that apply are the private key, the local certificate, the SSL protocol (SSLv2, SSLv3, TLSv1 where applicable) and the ciphers that the SSL backend is allowed to use.

    /PyQt-x11-gpl-4.4.4/doc/html/qnetworkrequest.html:72:

    By default, no SSL configuration is set, which allows the backends to choose freely what configuration is best for them.

    /PyQt-x11-gpl-4.4.4/doc/html/qnetworkrequest.html:76:

    QSslConfiguration QNetworkRequest.sslConfiguration (self)

    Returns this network request's SSL configuration. By default, no SSL settings are specified.

    /PyQt-x11-gpl-4.4.4/doc/html/qmetaobject.html:111: methods << QString.fromLatin1(metaObject->property(i).signature());
    /PyQt-x11-gpl-4.4.4/doc/html/qmetaobject.html:116:

    QByteArray QMetaObject.normalizedSignature (str method)

    Normalizes the signature of the given method.

    /PyQt-x11-gpl-4.4.4/doc/html/qssl.html:9:
      Home · All Classes · Modules

    QSsl Class Reference
    [QtNetwork module]

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

    /PyQt-x11-gpl-4.4.4/doc/html/qssl.html:10:

    Types


    Detailed Description

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

    /PyQt-x11-gpl-4.4.4/doc/html/qssl.html:27:QSsl.Rsa0The RSA algorithm. /PyQt-x11-gpl-4.4.4/doc/html/qssl.html:28:QSsl.Dsa1The DSA algorithm. /PyQt-x11-gpl-4.4.4/doc/html/qssl.html:45:

    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.

    /PyQt-x11-gpl-4.4.4/doc/html/qtxmlpatterns.html:220:httpsResources retrieved via HTTPS. This will succeed if no SSL errors are encountered. /PyQt-x11-gpl-4.4.4/doc/html/qtnetwork.html:67:

    QHostInfo provides a static function that lets you perform such a lookup yourself. By calling QHostInfo.lookupHost() with a host name, a QObject pointer, and a slot signature, QHostInfo will perform the name lookup and invoke the given slot when the results are ready. The actual lookup is done in a separate thread, making use of the operating system's own methods for performing name lookups.

    /PyQt-x11-gpl-4.4.4/doc/html/qdesignermembersheetextension.html:10:

    Inherited by QPyDesignerMemberSheetExtension.

    Methods


    Detailed Description

    The QDesignerMemberSheetExtension class allows you to manipulate a widget's member functions which is displayed when configuring connections using Qt Designer's mode for editing signals and slots.

    /PyQt-x11-gpl-4.4.4/doc/html/qdesignermembersheetextension.html:94:

    QString QDesignerMemberSheetExtension.signature (self, int index)

    This method is abstract and should be reimplemented in any sub-class.

    Returns the signature of the member function with the given index.

    /PyQt-x11-gpl-4.4.4/doc/html/qnetworkreply.html:25:QNetworkReply.SslHandshakeFailedError6the SSL/TLS handshake failed and the encrypted channel could not be established. The sslErrors() signal should have been emitted. /PyQt-x11-gpl-4.4.4/doc/html/qnetworkreply.html:94:

    QNetworkReply.setSslConfiguration (self, QSslConfiguration configuration)

    Sets the SSL configuration for the network connection associated with this request, if possible, to be that of config.

    /PyQt-x11-gpl-4.4.4/doc/html/qnetworkreply.html:98:

    QSslConfiguration QNetworkReply.sslConfiguration (self)

    Returns the SSL configuration and state associated with this reply, if SSL was used. It will contain the remote server's certificate, its certificate chain leading to the Certificate Authority as well as the encryption ciphers in use.

    /PyQt-x11-gpl-4.4.4/doc/html/qnetworkreply.html:120:

    void sslErrors (const QList<QSslError>&)

    This signal is emitted if the SSL/TLS session encountered errors during the set up, including certificate verification errors. The errors parameter contains the list of errors.

    /PyQt-x11-gpl-4.4.4/doc/html/qnetworkreply.html:121:

    To indicate that the errors are not fatal and that the connection should proceed, the ignoreSslErrors() function should be called from the slot connected to this signal. If it is not called, the SSL session will be torn down before any data is exchanged (including the URL).

    /PyQt-x11-gpl-4.4.4/doc/html/qnetworkreply.html:122:

    This signal can be used to display an error message to the user indicating that security may be compromised and display the SSL settings (see sslConfiguration() to obtain it). If the user decides to proceed after analyzing the remote certificate, the slot should call ignoreSslErrors().

    /PyQt-x11-gpl-4.4.4/doc/html/qsslerror.html:9:
      Home · All Classes · Modules

    QSslError Class Reference
    [QtNetwork module]

    The QSslError class provides an SSL error. More...

    /PyQt-x11-gpl-4.4.4/doc/html/qsslerror.html:10:

    Types

    Methods

    Special Methods


    Detailed Description

    The QSslError class provides an SSL error.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslerror.html:11:

    QSslError provides a simple API for managing errors during QSslSocket's SSL handshake.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslerror.html:13:

    Type Documentation

    QSslError.SslError

    Describes all recognized errors that can occur during an SSL handshake.

    /PyQt-x11-gpl-4.4.4/doc/html/qsslcipher.html:9:
      Home · All Classes · Modules

    QSslCipher Class Reference
    [
    QtNetwork module]

    The QSslCipher class represents an SSL cryptographic cipher. More...

    /PyQt-x11-gpl-4.4.4/doc/html/qsslcipher.html:10:

    Methods

    Special Methods


    Detailed Description

    The QSslCipher class represents an SSL cryptographic cipher.

    /PyQt-x11-gpl-4.4.4/doc/html/qabstractsocket.html:70:QAbstractSocket.SslHandshakeFailedError13The SSL/TLS handshake failed, so the connection was closed (only used in
    QSslSocket) /PyQt-x11-gpl-4.4.4/doc/html/qhttp.html:71:QHttp.ConnectionModeHttps1The Https protocol is used and the connection is encrypted using SSL. /PyQt-x11-gpl-4.4.4/doc/html/qhttp.html:73:

    When using the Https mode, care should be taken to connect to the sslErrors signal, and handle possible Ssl errors.

    /PyQt-x11-gpl-4.4.4/doc/html/qhttp.html:253:

    void sslErrors (const QList<QSslError>&)

    Forwards the sslErrors signal from the QSslSocket used in QHttp. errors is the list of errors that occurred during the SSL handshake. Unless you call ignoreSslErrors() from within a slot connected to this signal when an error occurs, QHttp will tear down the connection immediately after emitting the signal.

    /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.html:734:argument that is the name of the signal and its C++ signature. For example:

    /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.html:747:PyQt_PyObject as the type of the argument in the signature. For example:

    /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.html:774:argument that is the name of the slot and its C++ signature. For example:

    /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.html:828:function signature that a Python method emulates. PyQt provides the /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.html:830:

    The decorator takes a signature argument and an optional result /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.html:832:

    The signature is a comma separated list of C++ types representing each of /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.html:1264:strings each of which is the C++ signature (but excluding the return /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.html:1287:also behave as Python properties. The full signature of the function is /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.txt:415:argument that is the name of the signal and its C++ signature. For example:: /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.txt:431:``PyQt_PyObject`` as the type of the argument in the signature. For example:: /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.txt:465:argument that is the name of the slot and its C++ signature. For example:: /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.txt:527:function signature that a Python method emulates. PyQt provides the /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.txt:530:The decorator takes a ``signature`` argument and an optional ``result`` /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.txt:533:The ``signature`` is a comma separated list of C++ types representing each of /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.txt:989: strings each of which is the C++ signature (but excluding the return /PyQt-x11-gpl-4.4.4/doc/pyqt4ref.txt:1010: also behave as Python properties. The full signature of the function is /PyQt-x11-gpl-4.4.4/ChangeLog:362:signature if it finds it has a wrapped type. /PyQt-x11-gpl-4.4.4/ChangeLog:474:Added a missing OpenSSL guard. /PyQt-x11-gpl-4.4.4/ChangeLog:526:Added the tags that should allow building against Qt v4.4 without OpenSSL /PyQt-x11-gpl-4.4.4/ChangeLog:597:argument that allows the signature to have a return type. /PyQt-x11-gpl-4.4.4/ChangeLog:860:keyword argument to allow for future expansion of the signature. /PyQt-x11-gpl-4.4.4/ChangeLog:1162:The mega Windows GPL package now supports SSL. /PyQt-x11-gpl-4.4.4/ChangeLog:1345:The SSL support is now disabled if Qt was built without SSL support (thanks to /PyQt-x11-gpl-4.4.4/ChangeLog:1715:signature always has a method name. /PyQt-x11-gpl-4.4.4/ChangeLog:2483:Eliminated all conflicting overloads that had the same Python signature. /PyQt-x11-gpl-4.4.4/ChangeLog:2648:Renamed signature() as pyqtSignature() and added support for a short version of /PyQt-x11-gpl-4.4.4/ChangeLog:2649:the signature that only includes the argument types (without enclosing /PyQt-x11-gpl-4.4.4/ChangeLog:2655:Added the signature() decorator to QtCore. /PyQt-x11-gpl-4.4.4/ChangeLog:5176:Correction to signature of QDir.rename(). /PyQt-x11-gpl-4.4.4/GPL_EXCEPTION.TXT:43:OpenSSL license (with original /PyQt-x11-gpl-4.4.4/examples/xml/dombookmarks/frank.xbel:171: /PyQt-x11-gpl-4.4.4/examples/xml/dombookmarks/frank.xbel:174: /PyQt-x11-gpl-4.4.4/examples/xml/dombookmarks/jennifer.xbel:90: Dictionnaire des synonymes /PyQt-x11-gpl-4.4.4/examples/xml/saxbookmarks/frank.xbel:171: /PyQt-x11-gpl-4.4.4/examples/xml/saxbookmarks/frank.xbel:174: /PyQt-x11-gpl-4.4.4/examples/xml/saxbookmarks/jennifer.xbel:90: Dictionnaire des synonymes /PyQt-x11-gpl-4.4.4/examples/tools/codecs/encodedfiles/iso-8859-1.txt:5:Walter Moers: Die 13½ Leben des Käpt'n Blaubär /PyQt-x11-gpl-4.4.4/examples/mainwindows/dockwidgets/dockwidgets.py:244: << "Sally Hobart, Tiroli Tea, 67 Long River, Fedula") /PyQt-x11-gpl-4.4.4/configure.py:153: p.add_option("--mwg-openssl", action="callback", default=None, /PyQt-x11-gpl-4.4.4/configure.py:154: dest="mwg_ssl_dir", metavar="DIR", callback=store_abspath_dir, /PyQt-x11-gpl-4.4.4/configure.py:280: if opts.mwg_ssl_dir: /PyQt-x11-gpl-4.4.4/configure.py:281: ass_lib_dirs = [os.path.join(opts.mwg_ssl_dir, "lib")] /PyQt-x11-gpl-4.4.4/configure.py:511: if opts.mwg_ssl_dir: /PyQt-x11-gpl-4.4.4/configure.py:512: cons_xtra_libdirs.append(os.path.join(opts.mwg_ssl_dir, "lib")) /PyQt-x11-gpl-4.4.4/configure.py:1615:#if defined(QT_NO_OPENSSL) /PyQt-x11-gpl-4.4.4/configure.py:1616: out << "PyQt_OpenSSL\\n"; /PyQt-x11-gpl-4.4.4/sip/QtDesigner/membersheet.sip:58: virtual QString signature(int index) const = 0; /PyQt-x11-gpl-4.4.4/sip/QtCore/qglobal.sip:155: MV_TIGER, /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:578:SIP_PYOBJECT pyqtSignature(const char *signature, const char *result = 0) /NoArgParser/; /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:581: static const char *kwlist[] = {"signature", "result", 0}; /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:586: // Wrap the normalised signature and result type in a PyCObject. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:590: // Make sure the signature has parentheses before normalising it. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:624:// The signature attribute name as an object. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:625:extern PyObject *qtcore_signature_attr; /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:671:// The signature attribute name as an object. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:672:PyObject *qtcore_signature_attr; /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:1879: // signals: signature, parameters, type, tag, flags /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:1882: // slots: signature, parameters, type, tag, flags /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:1923: // signal of the right name and signature. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:1935: // - the name and full signature, less the initial type character, plus the /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:1945: + qstrlen(psig->sg_signature); /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:1972: qstrcpy(&smd[i], &psig->sg_signature[1]); /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:2226: const sipSignature *psig = slot_conn.sc_signature; /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:2428: if ((idx = otxmo->indexOfSignal(&psig->sg_signature[1])) < 0) /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:2439: idx = up->metaObject()->indexOfSignal(&psig->sg_signature[1]); /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:2456: PyErr_Format(PyExc_TypeError, "argument %d of signal %s.%s has an invalid type", a, otxmo->className(), &psig->sg_signature[1]); /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3246:// This is the decorator function that saves the C++ signature as a function /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3255: // See if the signature contains a method name. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3271: if (PyObject_SetAttr(f, qtcore_signature_attr, self) < 0) /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3334:// Add the (non-existent) argument names for a signature and return their index /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3394: // anything with a PyQt signature) or a sequence of signals. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3407: PyObject *args_obj = PyObject_GetAttr(value, qtcore_signature_attr); /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3422: // Parse the signature and result. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3440: conn->sc_signature = sipParseSignature(args->first.data()); /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3442: if (!conn->sc_signature) /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3569: // Add the full signature. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3584: const char *sig = slot.args.sc_signature->sg_signature; /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:3589: // Add the full signature. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:4082:qtcore_signature_attr = PyString_FromString("__pyqtSignature__"); /PyQt-x11-gpl-4.4.4/sip/QtCore/qobject.sip:4084:if (!qtcore_signature_attr) /PyQt-x11-gpl-4.4.4/sip/QtCore/QtCoremod.sip:51:%Feature PyQt_OpenSSL /PyQt-x11-gpl-4.4.4/sip/QtCore/qcryptographichash.sip:50: Md4, /PyQt-x11-gpl-4.4.4/sip/QtCore/qcryptographichash.sip:51: Md5, /PyQt-x11-gpl-4.4.4/sip/QtCore/qcryptographichash.sip:52: Sha1, /PyQt-x11-gpl-4.4.4/sip/QtCore/qiodevice.sip:119: // The two C++ overloads would have the same Python signature so we get most of /PyQt-x11-gpl-4.4.4/sip/QtCore/qmetaobject.sip:47: const char *signature() const; /PyQt-x11-gpl-4.4.4/sip/QtCore/qobjectdefs.sip:105: // Use the signature attribute instead of the name if there is one. /PyQt-x11-gpl-4.4.4/sip/QtCore/qobjectdefs.sip:106: PyObject *sigattr = PyObject_GetAttr(slot_obj, qtcore_signature_attr); /PyQt-x11-gpl-4.4.4/sip/QtCore/qobjectdefs.sip:169: QByteArray sig(mm.signature()); /PyQt-x11-gpl-4.4.4/sip/QtScript/qscriptengine.sip:144: QScriptValue newFunction(SIP_PYCALLABLE signature, int length = 0); /PyQt-x11-gpl-4.4.4/sip/QtScript/qscriptengine.sip:158: QScriptValue newFunction(SIP_PYCALLABLE signature, const QScriptValue &prototype, int length = 0); /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qnetworkrequest.sip:91:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qnetworkrequest.sip:94:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslsocket.sip:39:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslsocket.sip:78: void setPrivateKey(const QString &fileName, QSsl::KeyAlgorithm algorithm = QSsl::Rsa, QSsl::EncodingFormat format = QSsl::Pem, const QByteArray &passPhrase = QByteArray()); /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qssl.sip:39:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qssl.sip:61: Rsa, /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qssl.sip:62: Dsa, /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslconfiguration.sip:39:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qnetworkaccessmanager.sip:73:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslcertificate.sip:39:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslcertificate.sip:70: QByteArray digest(QCryptographicHash::Algorithm algorithm = QCryptographicHash::Md5) const; /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslcertificate.sip:90:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qabstractsocket.sip:82: #if QT_VERSION >= 0x040300 && !defined(QT_NO_OPENSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslkey.sip:39:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qnetworkreply.sip:90:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qnetworkreply.sip:93:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qnetworkreply.sip:104:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qhttp.sip:243:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qhttp.sip:264:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslcipher.sip:39:%If (PyQt_OpenSSL) /PyQt-x11-gpl-4.4.4/sip/QtNetwork/qsslerror.sip:39:%If (PyQt_OpenSSL)