ssl
— TLS/SSL wrapper for socket objects¶
Source code:Lib/ssl.py
This module provides access to Transport Layer Security (often known as «SecureSockets Layer») encryption and peer authentication facilities for networksockets, both client-side and server-side. This module uses the OpenSSLlibrary. It is available on all modern Unix systems, Windows, macOS, andprobably additional platforms, as long as OpenSSL is installed on that platform.
Σημείωση
Some behavior may be platform dependent, since calls are made to theoperating system socket APIs. The installed version of OpenSSL may alsocause variations in behavior. For example, TLSv1.3 comes with OpenSSL version1.1.1.
Προειδοποίηση
Don’t use this module without reading theSecurity considerations. Doing somay lead to a false sense of security, as the default settings of thessl module are not necessarily appropriate for your application.
Διαθεσιμότητα: not WASI.
This module does not work or is not available on WebAssembly. SeeWebAssembly platforms for more information.
This section documents the objects and functions in thessl
module; for moregeneral information about TLS, SSL, and certificates, the reader is referred tothe documents in the «See Also» section at the bottom.
This module provides a class,ssl.SSLSocket
, which is derived from thesocket.socket
type, and provides a socket-like wrapper that alsoencrypts and decrypts the data going over the socket with SSL. It supportsadditional methods such asgetpeercert()
, which retrieves thecertificate of the other side of the connection,cipher()
, whichretrieves the cipher being used for the secure connection orget_verified_chain()
,get_unverified_chain()
which retrievescertificate chain.
For more sophisticated applications, thessl.SSLContext
classhelps manage settings and certificates, which can then be inheritedby SSL sockets created through theSSLContext.wrap_socket()
method.
Άλλαξε στην έκδοση 3.5.3:Updated to support linking with OpenSSL 1.1.0
Άλλαξε στην έκδοση 3.6:OpenSSL 0.9.8, 1.0.0 and 1.0.1 are deprecated and no longer supported.In the future the ssl module will require at least OpenSSL 1.0.2 or1.1.0.
Άλλαξε στην έκδοση 3.10:PEP 644 has been implemented. The ssl module requires OpenSSL 1.1.1or newer.
Use of deprecated constants and functions result in deprecation warnings.
Functions, Constants, and Exceptions¶
Socket creation¶
Instances ofSSLSocket
must be created using theSSLContext.wrap_socket()
method. The helper functioncreate_default_context()
returns a new context with secure defaultsettings.
Client socket example with default context and IPv4/IPv6 dual stack:
importsocketimportsslhostname='www.python.org'context=ssl.create_default_context()withsocket.create_connection((hostname,443))assock:withcontext.wrap_socket(sock,server_hostname=hostname)asssock:print(ssock.version())
Client socket example with custom context and IPv4:
hostname='www.python.org'# PROTOCOL_TLS_CLIENT requires valid cert chain and hostnamecontext=ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)context.load_verify_locations('path/to/cabundle.pem')withsocket.socket(socket.AF_INET,socket.SOCK_STREAM,0)assock:withcontext.wrap_socket(sock,server_hostname=hostname)asssock:print(ssock.version())
Server socket example listening on localhost IPv4:
context=ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)context.load_cert_chain('/path/to/certchain.pem','/path/to/private.key')withsocket.socket(socket.AF_INET,socket.SOCK_STREAM,0)assock:sock.bind(('127.0.0.1',8443))sock.listen(5)withcontext.wrap_socket(sock,server_side=True)asssock:conn,addr=ssock.accept()...
Context creation¶
A convenience function helps createSSLContext
objects for commonpurposes.
- ssl.create_default_context(purpose=Purpose.SERVER_AUTH,cafile=None,capath=None,cadata=None)¶
Return a new
SSLContext
object with default settings forthe givenpurpose. The settings are chosen by thessl
module,and usually represent a higher security level than when calling theSSLContext
constructor directly.cafile,capath,cadata represent optional CA certificates totrust for certificate verification, as in
SSLContext.load_verify_locations()
. If all three areNone
, this function can choose to trust the system’s defaultCA certificates instead.The settings are:
PROTOCOL_TLS_CLIENT
orPROTOCOL_TLS_SERVER
,OP_NO_SSLv2
, andOP_NO_SSLv3
with high encryption cipher suites without RC4 andwithout unauthenticated cipher suites. PassingSERVER_AUTH
aspurpose setsverify_mode
toCERT_REQUIRED
and either loads CA certificates (when at least one ofcafile,capath orcadata is given) or usesSSLContext.load_default_certs()
to loaddefault CA certificates.When
keylog_filename
is supported and the environmentvariableSSLKEYLOGFILE
is set,create_default_context()
enables key logging.The default settings for this context include
VERIFY_X509_PARTIAL_CHAIN
andVERIFY_X509_STRICT
.These make the underlying OpenSSL implementation behave more likea conforming implementation ofRFC 5280, in exchange for a smallamount of incompatibility with older X.509 certificates.Σημείωση
The protocol, options, cipher and other settings may change to morerestrictive values anytime without prior deprecation. The valuesrepresent a fair balance between compatibility and security.
If your application needs specific settings, you should create a
SSLContext
and apply the settings yourself.Σημείωση
If you find that when certain older clients or servers attempt to connectwith a
SSLContext
created by this function that they get an errorstating «Protocol or cipher suite mismatch», it may be that they onlysupport SSL3.0 which this function excludes using theOP_NO_SSLv3
. SSL3.0 is widely considered to becompletely broken. If you still wish to continue touse this function but still allow SSL 3.0 connections you can re-enablethem using:ctx=ssl.create_default_context(Purpose.CLIENT_AUTH)ctx.options&=~ssl.OP_NO_SSLv3
Σημείωση
This context enables
VERIFY_X509_STRICT
by default, whichmay reject pre-RFC 5280 or malformed certificates that theunderlying OpenSSL implementation otherwise would accept. While disablingthis is not recommended, you can do so using:ctx=ssl.create_default_context()ctx.verify_flags&=~ssl.VERIFY_X509_STRICT
Added in version 3.4.
Άλλαξε στην έκδοση 3.4.4:RC4 was dropped from the default cipher string.
Άλλαξε στην έκδοση 3.6:ChaCha20/Poly1305 was added to the default cipher string.
3DES was dropped from the default cipher string.
Άλλαξε στην έκδοση 3.8:Support for key logging to
SSLKEYLOGFILE
was added.Άλλαξε στην έκδοση 3.10:The context now uses
PROTOCOL_TLS_CLIENT
orPROTOCOL_TLS_SERVER
protocol instead of genericPROTOCOL_TLS
.Άλλαξε στην έκδοση 3.13:The context now uses
VERIFY_X509_PARTIAL_CHAIN
andVERIFY_X509_STRICT
in its default verify flags.
Exceptions¶
- exceptionssl.SSLError¶
Raised to signal an error from the underlying SSL implementation(currently provided by the OpenSSL library). This signifies someproblem in the higher-level encryption and authentication layer that’ssuperimposed on the underlying network connection. This erroris a subtype of
OSError
. The error code and message ofSSLError
instances are provided by the OpenSSL library.Άλλαξε στην έκδοση 3.3:
SSLError
used to be a subtype ofsocket.error
.- library¶
A string mnemonic designating the OpenSSL submodule in which the erroroccurred, such as
SSL
,PEM
orX509
. The range of possiblevalues depends on the OpenSSL version.Added in version 3.3.
- reason¶
A string mnemonic designating the reason this error occurred, forexample
CERTIFICATE_VERIFY_FAILED
. The range of possiblevalues depends on the OpenSSL version.Added in version 3.3.
- exceptionssl.SSLZeroReturnError¶
A subclass of
SSLError
raised when trying to read or write andthe SSL connection has been closed cleanly. Note that this doesn’tmean that the underlying transport (read TCP) has been closed.Added in version 3.3.
- exceptionssl.SSLWantReadError¶
A subclass of
SSLError
raised by anon-blocking SSL socket when trying to read or write data, but more data needsto be received on the underlying TCP transport before the request can befulfilled.Added in version 3.3.
- exceptionssl.SSLWantWriteError¶
A subclass of
SSLError
raised by anon-blocking SSL socket when trying to read or write data, but more data needsto be sent on the underlying TCP transport before the request can befulfilled.Added in version 3.3.
- exceptionssl.SSLSyscallError¶
A subclass of
SSLError
raised when a system error was encounteredwhile trying to fulfill an operation on a SSL socket. Unfortunately,there is no easy way to inspect the original errno number.Added in version 3.3.
- exceptionssl.SSLEOFError¶
A subclass of
SSLError
raised when the SSL connection has beenterminated abruptly. Generally, you shouldn’t try to reuse the underlyingtransport when this error is encountered.Added in version 3.3.
- exceptionssl.SSLCertVerificationError¶
A subclass of
SSLError
raised when certificate validation hasfailed.Added in version 3.7.
- verify_code¶
A numeric error number that denotes the verification error.
- verify_message¶
A human readable string of the verification error.
- exceptionssl.CertificateError¶
An alias for
SSLCertVerificationError
.Άλλαξε στην έκδοση 3.7:The exception is now an alias for
SSLCertVerificationError
.
Random generation¶
- ssl.RAND_bytes(num)¶
Returnnum cryptographically strong pseudo-random bytes. Raises an
SSLError
if the PRNG has not been seeded with enough data or if theoperation is not supported by the current RAND method.RAND_status()
can be used to check the status of the PRNG andRAND_add()
can be usedto seed the PRNG.For almost all applications
os.urandom()
is preferable.Read the Wikipedia article,Cryptographically secure pseudorandom numbergenerator (CSPRNG),to get the requirements of a cryptographically strong generator.
Added in version 3.3.
- ssl.RAND_status()¶
Return
True
if the SSL pseudo-random number generator has been seededwith “enough” randomness, andFalse
otherwise. You can usessl.RAND_egd()
andssl.RAND_add()
to increase the randomness ofthe pseudo-random number generator.
- ssl.RAND_add(bytes,entropy)¶
Mix the givenbytes into the SSL pseudo-random number generator. Theparameterentropy (a float) is a lower bound on the entropy contained instring (so you can always use
0.0
). SeeRFC 1750 for moreinformation on sources of entropy.Άλλαξε στην έκδοση 3.5:Writablebytes-like object is now accepted.
Certificate handling¶
- ssl.cert_time_to_seconds(cert_time)¶
Return the time in seconds since the Epoch, given the
cert_time
string representing the «notBefore» or «notAfter» date from acertificate in"%b%d%H:%M:%S%Y%Z"
strptime format (Clocale).Here’s an example:
>>>importssl>>>timestamp=ssl.cert_time_to_seconds("Jan 5 09:34:43 2018 GMT")>>>timestamp1515144883>>>fromdatetimeimportdatetime>>>print(datetime.utcfromtimestamp(timestamp))2018-01-05 09:34:43
«notBefore» or «notAfter» dates must use GMT (RFC 5280).
Άλλαξε στην έκδοση 3.5:Interpret the input time as a time in UTC as specified by “GMT”timezone in the input string. Local timezone was usedpreviously. Return an integer (no fractions of a second in theinput format)
- ssl.get_server_certificate(addr,ssl_version=PROTOCOL_TLS_CLIENT,ca_certs=None[,timeout])¶
Given the address
addr
of an SSL-protected server, as a (hostname,port-number) pair, fetches the server’s certificate, and returns it as aPEM-encoded string. Ifssl_version
is specified, uses that version ofthe SSL protocol to attempt to connect to the server. Ifca_certs isspecified, it should be a file containing a list of root certificates, thesame format as used for thecafile parameter inSSLContext.load_verify_locations()
. The call will attempt to validate theserver certificate against that set of root certificates, and will failif the validation attempt fails. A timeout can be specified with thetimeout
parameter.Άλλαξε στην έκδοση 3.3:This function is now IPv6-compatible.
Άλλαξε στην έκδοση 3.5:The defaultssl_version is changed from
PROTOCOL_SSLv3
toPROTOCOL_TLS
for maximum compatibility with modern servers.Άλλαξε στην έκδοση 3.10:Thetimeout parameter was added.
- ssl.DER_cert_to_PEM_cert(DER_cert_bytes)¶
Given a certificate as a DER-encoded blob of bytes, returns a PEM-encodedstring version of the same certificate.
- ssl.PEM_cert_to_DER_cert(PEM_cert_string)¶
Given a certificate as an ASCII PEM string, returns a DER-encoded sequence ofbytes for that same certificate.
- ssl.get_default_verify_paths()¶
Returns a named tuple with paths to OpenSSL’s default cafile and capath.The paths are the same as used by
SSLContext.set_default_verify_paths()
. The return value is anamed tupleDefaultVerifyPaths
:cafile
- resolved path to cafile orNone
if the file doesn’t exist,capath
- resolved path to capath orNone
if the directory doesn’t exist,openssl_cafile_env
- OpenSSL’s environment key that points to a cafile,openssl_cafile
- hard coded path to a cafile,openssl_capath_env
- OpenSSL’s environment key that points to a capath,openssl_capath
- hard coded path to a capath directory
Added in version 3.4.
- ssl.enum_certificates(store_name)¶
Retrieve certificates from Windows” system cert store.store_name may beone of
CA
,ROOT
orMY
. Windows may provide additional certstores, too.The function returns a list of (cert_bytes, encoding_type, trust) tuples.The encoding_type specifies the encoding of cert_bytes. It is either
x509_asn
for X.509 ASN.1 data orpkcs_7_asn
forPKCS#7 ASN.1 data. Trust specifies the purpose of the certificate as a setof OIDS or exactlyTrue
if the certificate is trustworthy for allpurposes.Example:
>>>ssl.enum_certificates("CA")[(b'data...', 'x509_asn', {'1.3.6.1.5.5.7.3.1', '1.3.6.1.5.5.7.3.2'}), (b'data...', 'x509_asn', True)]
Διαθεσιμότητα: Windows.
Added in version 3.4.
- ssl.enum_crls(store_name)¶
Retrieve CRLs from Windows” system cert store.store_name may beone of
CA
,ROOT
orMY
. Windows may provide additional certstores, too.The function returns a list of (cert_bytes, encoding_type, trust) tuples.The encoding_type specifies the encoding of cert_bytes. It is either
x509_asn
for X.509 ASN.1 data orpkcs_7_asn
forPKCS#7 ASN.1 data.Διαθεσιμότητα: Windows.
Added in version 3.4.
Constants¶
All constants are now
enum.IntEnum
orenum.IntFlag
collections.Added in version 3.6.
- ssl.CERT_NONE¶
Possible value for
SSLContext.verify_mode
.Except forPROTOCOL_TLS_CLIENT
,it is the default mode. With client-side sockets, just about anycert is accepted. Validation errors, such as untrusted or expired cert,are ignored and do not abort the TLS/SSL handshake.In server mode, no certificate is requested from the client, so the clientdoes not send any for client cert authentication.
See the discussion ofSecurity considerations below.
- ssl.CERT_OPTIONAL¶
Possible value for
SSLContext.verify_mode
.In client mode,CERT_OPTIONAL
has the same meaning asCERT_REQUIRED
. It is recommended touseCERT_REQUIRED
for client-side sockets instead.In server mode, a client certificate request is sent to the client. Theclient may either ignore the request or send a certificate in orderperform TLS client cert authentication. If the client chooses to senda certificate, it is verified. Any verification error immediately abortsthe TLS handshake.
Use of this setting requires a valid set of CA certificates tobe passed to
SSLContext.load_verify_locations()
.
- ssl.CERT_REQUIRED¶
Possible value for
SSLContext.verify_mode
.In this mode, certificates arerequired from the other side of the socket connection; anSSLError
will be raised if no certificate is provided, or if its validation fails.This mode isnot sufficient to verify a certificate in client mode asit does not match hostnames.check_hostname
must beenabled as well to verify the authenticity of a cert.PROTOCOL_TLS_CLIENT
usesCERT_REQUIRED
andenablescheck_hostname
by default.With server socket, this mode provides mandatory TLS client certauthentication. A client certificate request is sent to the client andthe client must provide a valid and trusted certificate.
Use of this setting requires a valid set of CA certificates tobe passed to
SSLContext.load_verify_locations()
.
- classssl.VerifyMode¶
enum.IntEnum
collection of CERT_* constants.Added in version 3.6.
- ssl.VERIFY_DEFAULT¶
Possible value for
SSLContext.verify_flags
. In this mode, certificaterevocation lists (CRLs) are not checked. By default OpenSSL does neitherrequire nor verify CRLs.Added in version 3.4.
- ssl.VERIFY_CRL_CHECK_LEAF¶
Possible value for
SSLContext.verify_flags
. In this mode, only thepeer cert is checked but none of the intermediate CA certificates. The moderequires a valid CRL that is signed by the peer cert’s issuer (its directancestor CA). If no proper CRL has been loaded withSSLContext.load_verify_locations
, validation will fail.Added in version 3.4.
- ssl.VERIFY_CRL_CHECK_CHAIN¶
Possible value for
SSLContext.verify_flags
. In this mode, CRLs ofall certificates in the peer cert chain are checked.Added in version 3.4.
- ssl.VERIFY_X509_STRICT¶
Possible value for
SSLContext.verify_flags
to disable workaroundsfor broken X.509 certificates.Added in version 3.4.
- ssl.VERIFY_ALLOW_PROXY_CERTS¶
Possible value for
SSLContext.verify_flags
to enables proxycertificate verification.Added in version 3.10.
- ssl.VERIFY_X509_TRUSTED_FIRST¶
Possible value for
SSLContext.verify_flags
. It instructs OpenSSL toprefer trusted certificates when building the trust chain to validate acertificate. This flag is enabled by default.Added in version 3.4.4.
- ssl.VERIFY_X509_PARTIAL_CHAIN¶
Possible value for
SSLContext.verify_flags
. It instructs OpenSSL toaccept intermediate CAs in the trust store to be treated as trust-anchors,in the same way as the self-signed root CA certificates. This makes itpossible to trust certificates issued by an intermediate CA without havingto trust its ancestor root CA.Added in version 3.10.
- classssl.VerifyFlags¶
enum.IntFlag
collection of VERIFY_* constants.Added in version 3.6.
- ssl.PROTOCOL_TLS¶
Selects the highest protocol version that both the client and server support.Despite the name, this option can select both «SSL» and «TLS» protocols.
Added in version 3.6.
Αποσύρθηκε στην έκδοση 3.10:TLS clients and servers require different default settings for securecommunication. The generic TLS protocol constant is deprecated infavor of
PROTOCOL_TLS_CLIENT
andPROTOCOL_TLS_SERVER
.
- ssl.PROTOCOL_TLS_CLIENT¶
Auto-negotiate the highest protocol version that both the client andserver support, and configure the context client-side connections. Theprotocol enables
CERT_REQUIRED
andcheck_hostname
by default.Added in version 3.6.
- ssl.PROTOCOL_TLS_SERVER¶
Auto-negotiate the highest protocol version that both the client andserver support, and configure the context server-side connections.
Added in version 3.6.
- ssl.PROTOCOL_SSLv23¶
Alias for
PROTOCOL_TLS
.Αποσύρθηκε στην έκδοση 3.6:Use
PROTOCOL_TLS
instead.
- ssl.PROTOCOL_SSLv3¶
Selects SSL version 3 as the channel encryption protocol.
This protocol is not available if OpenSSL is compiled with the
no-ssl3
option.Προειδοποίηση
SSL version 3 is insecure. Its use is highly discouraged.
Αποσύρθηκε στην έκδοση 3.6:OpenSSL has deprecated all version specific protocols. Use the defaultprotocol
PROTOCOL_TLS_SERVER
orPROTOCOL_TLS_CLIENT
withSSLContext.minimum_version
andSSLContext.maximum_version
instead.
- ssl.PROTOCOL_TLSv1¶
Selects TLS version 1.0 as the channel encryption protocol.
Αποσύρθηκε στην έκδοση 3.6:OpenSSL has deprecated all version specific protocols.
- ssl.PROTOCOL_TLSv1_1¶
Selects TLS version 1.1 as the channel encryption protocol.Available only with openssl version 1.0.1+.
Added in version 3.4.
Αποσύρθηκε στην έκδοση 3.6:OpenSSL has deprecated all version specific protocols.
- ssl.PROTOCOL_TLSv1_2¶
Selects TLS version 1.2 as the channel encryption protocol.Available only with openssl version 1.0.1+.
Added in version 3.4.
Αποσύρθηκε στην έκδοση 3.6:OpenSSL has deprecated all version specific protocols.
- ssl.OP_ALL¶
Enables workarounds for various bugs present in other SSL implementations.This option is set by default. It does not necessarily set the sameflags as OpenSSL’s
SSL_OP_ALL
constant.Added in version 3.2.
- ssl.OP_NO_SSLv2¶
Prevents an SSLv2 connection. This option is only applicable inconjunction with
PROTOCOL_TLS
. It prevents the peers fromchoosing SSLv2 as the protocol version.Added in version 3.2.
Αποσύρθηκε στην έκδοση 3.6:SSLv2 is deprecated
- ssl.OP_NO_SSLv3¶
Prevents an SSLv3 connection. This option is only applicable inconjunction with
PROTOCOL_TLS
. It prevents the peers fromchoosing SSLv3 as the protocol version.Added in version 3.2.
Αποσύρθηκε στην έκδοση 3.6:SSLv3 is deprecated
- ssl.OP_NO_TLSv1¶
Prevents a TLSv1 connection. This option is only applicable inconjunction with
PROTOCOL_TLS
. It prevents the peers fromchoosing TLSv1 as the protocol version.Added in version 3.2.
Αποσύρθηκε στην έκδοση 3.7:The option is deprecated since OpenSSL 1.1.0, use the new
SSLContext.minimum_version
andSSLContext.maximum_version
instead.
- ssl.OP_NO_TLSv1_1¶
Prevents a TLSv1.1 connection. This option is only applicable in conjunctionwith
PROTOCOL_TLS
. It prevents the peers from choosing TLSv1.1 asthe protocol version. Available only with openssl version 1.0.1+.Added in version 3.4.
Αποσύρθηκε στην έκδοση 3.7:The option is deprecated since OpenSSL 1.1.0.
- ssl.OP_NO_TLSv1_2¶
Prevents a TLSv1.2 connection. This option is only applicable in conjunctionwith
PROTOCOL_TLS
. It prevents the peers from choosing TLSv1.2 asthe protocol version. Available only with openssl version 1.0.1+.Added in version 3.4.
Αποσύρθηκε στην έκδοση 3.7:The option is deprecated since OpenSSL 1.1.0.
- ssl.OP_NO_TLSv1_3¶
Prevents a TLSv1.3 connection. This option is only applicable in conjunctionwith
PROTOCOL_TLS
. It prevents the peers from choosing TLSv1.3 asthe protocol version. TLS 1.3 is available with OpenSSL 1.1.1 or later.When Python has been compiled against an older version of OpenSSL, theflag defaults to0.Added in version 3.6.3.
Αποσύρθηκε στην έκδοση 3.7:The option is deprecated since OpenSSL 1.1.0. It was added to 2.7.15 and3.6.3 for backwards compatibility with OpenSSL 1.0.2.
- ssl.OP_NO_RENEGOTIATION¶
Disable all renegotiation in TLSv1.2 and earlier. Do not sendHelloRequest messages, and ignore renegotiation requests via ClientHello.
This option is only available with OpenSSL 1.1.0h and later.
Added in version 3.7.
- ssl.OP_CIPHER_SERVER_PREFERENCE¶
Use the server’s cipher ordering preference, rather than the client’s.This option has no effect on client sockets and SSLv2 server sockets.
Added in version 3.3.
- ssl.OP_SINGLE_DH_USE¶
Prevents reuse of the same DH key for distinct SSL sessions. Thisimproves forward secrecy but requires more computational resources.This option only applies to server sockets.
Added in version 3.3.
- ssl.OP_SINGLE_ECDH_USE¶
Prevents reuse of the same ECDH key for distinct SSL sessions. Thisimproves forward secrecy but requires more computational resources.This option only applies to server sockets.
Added in version 3.3.
- ssl.OP_ENABLE_MIDDLEBOX_COMPAT¶
Send dummy Change Cipher Spec (CCS) messages in TLS 1.3 handshake to makea TLS 1.3 connection look more like a TLS 1.2 connection.
This option is only available with OpenSSL 1.1.1 and later.
Added in version 3.8.
- ssl.OP_NO_COMPRESSION¶
Disable compression on the SSL channel. This is useful if the applicationprotocol supports its own compression scheme.
Added in version 3.3.
- classssl.Options¶
enum.IntFlag
collection of OP_* constants.
- ssl.OP_NO_TICKET¶
Prevent client side from requesting a session ticket.
Added in version 3.6.
- ssl.OP_IGNORE_UNEXPECTED_EOF¶
Ignore unexpected shutdown of TLS connections.
This option is only available with OpenSSL 3.0.0 and later.
Added in version 3.10.
- ssl.OP_ENABLE_KTLS¶
Enable the use of the kernel TLS. To benefit from the feature, OpenSSL musthave been compiled with support for it, and the negotiated cipher suites andextensions must be supported by it (a list of supported ones may vary byplatform and kernel version).
Note that with enabled kernel TLS some cryptographic operations areperformed by the kernel directly and not via any available OpenSSLProviders. This might be undesirable if, for example, the applicationrequires all cryptographic operations to be performed by the FIPS provider.
This option is only available with OpenSSL 3.0.0 and later.
Added in version 3.12.
- ssl.OP_LEGACY_SERVER_CONNECT¶
Allow legacy insecure renegotiation between OpenSSL and unpatched serversonly.
Added in version 3.12.
- ssl.HAS_ALPN¶
Whether the OpenSSL library has built-in support for theApplication-LayerProtocol Negotiation TLS extension as described inRFC 7301.
Added in version 3.5.
- ssl.HAS_NEVER_CHECK_COMMON_NAME¶
Whether the OpenSSL library has built-in support not checking subjectcommon name and
SSLContext.hostname_checks_common_name
iswriteable.Added in version 3.7.
- ssl.HAS_ECDH¶
Whether the OpenSSL library has built-in support for the Elliptic Curve-basedDiffie-Hellman key exchange. This should be true unless the feature wasexplicitly disabled by the distributor.
Added in version 3.3.
- ssl.HAS_SNI¶
Whether the OpenSSL library has built-in support for theServer NameIndication extension (as defined inRFC 6066).
Added in version 3.2.
- ssl.HAS_NPN¶
Whether the OpenSSL library has built-in support for theNext ProtocolNegotiation as described in theApplication Layer ProtocolNegotiation.When true, you can use the
SSLContext.set_npn_protocols()
method to advertisewhich protocols you want to support.Added in version 3.3.
- ssl.HAS_SSLv2¶
Whether the OpenSSL library has built-in support for the SSL 2.0 protocol.
Added in version 3.7.
- ssl.HAS_SSLv3¶
Whether the OpenSSL library has built-in support for the SSL 3.0 protocol.
Added in version 3.7.
- ssl.HAS_TLSv1¶
Whether the OpenSSL library has built-in support for the TLS 1.0 protocol.
Added in version 3.7.
- ssl.HAS_TLSv1_1¶
Whether the OpenSSL library has built-in support for the TLS 1.1 protocol.
Added in version 3.7.
- ssl.HAS_TLSv1_2¶
Whether the OpenSSL library has built-in support for the TLS 1.2 protocol.
Added in version 3.7.
- ssl.HAS_TLSv1_3¶
Whether the OpenSSL library has built-in support for the TLS 1.3 protocol.
Added in version 3.7.
- ssl.HAS_PSK¶
Whether the OpenSSL library has built-in support for TLS-PSK.
Added in version 3.13.
- ssl.HAS_PHA¶
Whether the OpenSSL library has built-in support for TLS-PHA.
Added in version 3.14.
- ssl.CHANNEL_BINDING_TYPES¶
List of supported TLS channel binding types. Strings in this listcan be used as arguments to
SSLSocket.get_channel_binding()
.Added in version 3.3.
- ssl.OPENSSL_VERSION¶
The version string of the OpenSSL library loaded by the interpreter:
>>>ssl.OPENSSL_VERSION'OpenSSL 1.0.2k 26 Jan 2017'
Added in version 3.2.
- ssl.OPENSSL_VERSION_INFO¶
A tuple of five integers representing version information about theOpenSSL library:
>>>ssl.OPENSSL_VERSION_INFO(1, 0, 2, 11, 15)
Added in version 3.2.
- ssl.OPENSSL_VERSION_NUMBER¶
The raw version number of the OpenSSL library, as a single integer:
>>>ssl.OPENSSL_VERSION_NUMBER268443839>>>hex(ssl.OPENSSL_VERSION_NUMBER)'0x100020bf'
Added in version 3.2.
- ssl.ALERT_DESCRIPTION_HANDSHAKE_FAILURE¶
- ssl.ALERT_DESCRIPTION_INTERNAL_ERROR¶
- ALERT_DESCRIPTION_*
Alert Descriptions fromRFC 5246 and others. TheIANA TLS Alert Registrycontains this list and references to the RFCs where their meaning is defined.
Used as the return value of the callback function in
SSLContext.set_servername_callback()
.Added in version 3.4.
- classssl.AlertDescription¶
enum.IntEnum
collection of ALERT_DESCRIPTION_* constants.Added in version 3.6.
- Purpose.SERVER_AUTH¶
Option for
create_default_context()
andSSLContext.load_default_certs()
. This value indicates that thecontext may be used to authenticate web servers (therefore, it willbe used to create client-side sockets).Added in version 3.4.
- Purpose.CLIENT_AUTH¶
Option for
create_default_context()
andSSLContext.load_default_certs()
. This value indicates that thecontext may be used to authenticate web clients (therefore, it willbe used to create server-side sockets).Added in version 3.4.
- classssl.SSLErrorNumber¶
enum.IntEnum
collection of SSL_ERROR_* constants.Added in version 3.6.
- classssl.TLSVersion¶
enum.IntEnum
collection of SSL and TLS versions forSSLContext.maximum_version
andSSLContext.minimum_version
.Added in version 3.7.
- TLSVersion.MINIMUM_SUPPORTED¶
- TLSVersion.MAXIMUM_SUPPORTED¶
The minimum or maximum supported SSL or TLS version. These are magicconstants. Their values don’t reflect the lowest and highest availableTLS/SSL versions.
- TLSVersion.SSLv3¶
- TLSVersion.TLSv1¶
- TLSVersion.TLSv1_1¶
- TLSVersion.TLSv1_2¶
- TLSVersion.TLSv1_3¶
SSL 3.0 to TLS 1.3.
Αποσύρθηκε στην έκδοση 3.10:All
TLSVersion
members exceptTLSVersion.TLSv1_2
andTLSVersion.TLSv1_3
are deprecated.
SSL Sockets¶
- classssl.SSLSocket(socket.socket)¶
SSL sockets provide the following methods ofSocket Objects:
recv()
,recv_into()
(but passing a non-zeroflags
argument is not allowed)sendfile()
(butos.sendfile
will be usedfor plain-text sockets only, elsesend()
will be used)
However, since the SSL (and TLS) protocol has its own framing atopof TCP, the SSL sockets abstraction can, in certain respects, diverge fromthe specification of normal, OS-level sockets. See especially thenotes on non-blocking sockets.
Instances of
SSLSocket
must be created using theSSLContext.wrap_socket()
method.Άλλαξε στην έκδοση 3.5:The
sendfile()
method was added.Άλλαξε στην έκδοση 3.5:The
shutdown()
does not reset the socket timeout each time bytesare received or sent. The socket timeout is now the maximum total durationof the shutdown.Αποσύρθηκε στην έκδοση 3.6:It is deprecated to create a
SSLSocket
instance directly, useSSLContext.wrap_socket()
to wrap a socket.Άλλαξε στην έκδοση 3.7:
SSLSocket
instances must to created withwrap_socket()
. In earlier versions, it was possibleto create instances directly. This was never documented or officiallysupported.Άλλαξε στην έκδοση 3.10:Python now uses
SSL_read_ex
andSSL_write_ex
internally. Thefunctions support reading and writing of data larger than 2 GB. Writingzero-length data no longer fails with a protocol violation error.
SSL sockets also have the following additional methods and attributes:
- SSLSocket.read(len=1024,buffer=None)¶
Read up tolen bytes of data from the SSL socket and return the result asa
bytes
instance. Ifbuffer is specified, then read into the bufferinstead, and return the number of bytes read.Raise
SSLWantReadError
orSSLWantWriteError
if the socket isnon-blocking and the read would block.As at any time a re-negotiation is possible, a call to
read()
can alsocause write operations.Άλλαξε στην έκδοση 3.5:The socket timeout is no longer reset each time bytes are received or sent.The socket timeout is now the maximum total duration to read up tolenbytes.
Αποσύρθηκε στην έκδοση 3.6:Use
recv()
instead ofread()
.
- SSLSocket.write(buf)¶
Writebuf to the SSL socket and return the number of bytes written. Thebuf argument must be an object supporting the buffer interface.
Raise
SSLWantReadError
orSSLWantWriteError
if the socket isnon-blocking and the write would block.As at any time a re-negotiation is possible, a call to
write()
canalso cause read operations.Άλλαξε στην έκδοση 3.5:The socket timeout is no longer reset each time bytes are received or sent.The socket timeout is now the maximum total duration to writebuf.
Αποσύρθηκε στην έκδοση 3.6:Use
send()
instead ofwrite()
.
Σημείωση
Theread()
andwrite()
methods are thelow-level methods that read and write unencrypted, application-level dataand decrypt/encrypt it to encrypted, wire-level data. These methodsrequire an active SSL connection, i.e. the handshake was completed andSSLSocket.unwrap()
was not called.
Normally you should use the socket API methods likerecv()
andsend()
instead of thesemethods.
- SSLSocket.do_handshake()¶
Perform the SSL setup handshake.
Άλλαξε στην έκδοση 3.4:The handshake method also performs
match_hostname()
when thecheck_hostname
attribute of the socket’scontext
is true.Άλλαξε στην έκδοση 3.5:The socket timeout is no longer reset each time bytes are received or sent.The socket timeout is now the maximum total duration of the handshake.
Άλλαξε στην έκδοση 3.7:Hostname or IP address is matched by OpenSSL during handshake. Thefunction
match_hostname()
is no longer used. In case OpenSSLrefuses a hostname or IP address, the handshake is aborted early anda TLS alert message is sent to the peer.
- SSLSocket.getpeercert(binary_form=False)¶
If there is no certificate for the peer on the other end of the connection,return
None
. If the SSL handshake hasn’t been done yet, raiseValueError
.If the
binary_form
parameter isFalse
, and a certificate wasreceived from the peer, this method returns adict
instance. If thecertificate was not validated, the dict is empty. If the certificate wasvalidated, it returns a dict with several keys, amongst themsubject
(the principal for which the certificate was issued) andissuer
(the principal issuing the certificate). If a certificate contains aninstance of theSubject Alternative Name extension (seeRFC 3280),there will also be asubjectAltName
key in the dictionary.The
subject
andissuer
fields are tuples containing the sequenceof relative distinguished names (RDNs) given in the certificate’s datastructure for the respective fields, and each RDN is a sequence ofname-value pairs. Here is a real-world example:{'issuer':((('countryName','IL'),),(('organizationName','StartCom Ltd.'),),(('organizationalUnitName','Secure Digital Certificate Signing'),),(('commonName','StartCom Class 2 Primary Intermediate Server CA'),)),'notAfter':'Nov 22 08:15:19 2013 GMT','notBefore':'Nov 21 03:09:52 2011 GMT','serialNumber':'95F0','subject':((('description','571208-SLe257oHY9fVQ07Z'),),(('countryName','US'),),(('stateOrProvinceName','California'),),(('localityName','San Francisco'),),(('organizationName','Electronic Frontier Foundation, Inc.'),),(('commonName','*.eff.org'),),(('emailAddress','hostmaster@eff.org'),)),'subjectAltName':(('DNS','*.eff.org'),('DNS','eff.org')),'version':3}
If the
binary_form
parameter isTrue
, and a certificate wasprovided, this method returns the DER-encoded form of the entire certificateas a sequence of bytes, orNone
if the peer did not provide acertificate. Whether the peer provides a certificate depends on the SSLsocket’s role:for a client SSL socket, the server will always provide a certificate,regardless of whether validation was required;
for a server SSL socket, the client will only provide a certificatewhen requested by the server; therefore
getpeercert()
will returnNone
if you usedCERT_NONE
(rather thanCERT_OPTIONAL
orCERT_REQUIRED
).
See also
SSLContext.check_hostname
.Άλλαξε στην έκδοση 3.2:The returned dictionary includes additional items such as
issuer
andnotBefore
.Άλλαξε στην έκδοση 3.4:
ValueError
is raised when the handshake isn’t done.The returned dictionary includes additional X509v3 extension items such ascrlDistributionPoints
,caIssuers
andOCSP
URIs.Άλλαξε στην έκδοση 3.9:IPv6 address strings no longer have a trailing new line.
- SSLSocket.get_verified_chain()¶
Returns verified certificate chain provided by the otherend of the SSL channel as a list of DER-encoded bytes.If certificate verification was disabled method acts the same as
get_unverified_chain()
.Added in version 3.13.
- SSLSocket.get_unverified_chain()¶
Returns raw certificate chain provided by the otherend of the SSL channel as a list of DER-encoded bytes.
Added in version 3.13.
- SSLSocket.cipher()¶
Returns a three-value tuple containing the name of the cipher being used, theversion of the SSL protocol that defines its use, and the number of secretbits being used. If no connection has been established, returns
None
.
- SSLSocket.shared_ciphers()¶
Return the list of ciphers available in both the client and server. Eachentry of the returned list is a three-value tuple containing the name of thecipher, the version of the SSL protocol that defines its use, and the numberof secret bits the cipher uses.
shared_ciphers()
returnsNone
if no connection has been established or the socket is a clientsocket.Added in version 3.5.
- SSLSocket.compression()¶
Return the compression algorithm being used as a string, or
None
if the connection isn’t compressed.If the higher-level protocol supports its own compression mechanism,you can use
OP_NO_COMPRESSION
to disable SSL-level compression.Added in version 3.3.
- SSLSocket.get_channel_binding(cb_type='tls-unique')¶
Get channel binding data for current connection, as a bytes object. Returns
None
if not connected or the handshake has not been completed.Thecb_type parameter allow selection of the desired channel bindingtype. Valid channel binding types are listed in the
CHANNEL_BINDING_TYPES
list. Currently only the “tls-unique” channelbinding, defined byRFC 5929, is supported.ValueError
will beraised if an unsupported channel binding type is requested.Added in version 3.3.
- SSLSocket.selected_alpn_protocol()¶
Return the protocol that was selected during the TLS handshake. If
SSLContext.set_alpn_protocols()
was not called, if the other party doesnot support ALPN, if this socket does not support any of the client’sproposed protocols, or if the handshake has not happened yet,None
isreturned.Added in version 3.5.
- SSLSocket.selected_npn_protocol()¶
Return the higher-level protocol that was selected during the TLS/SSLhandshake. If
SSLContext.set_npn_protocols()
was not called, orif the other party does not support NPN, or if the handshake has not yethappened, this will returnNone
.Added in version 3.3.
Αποσύρθηκε στην έκδοση 3.10:NPN has been superseded by ALPN
- SSLSocket.unwrap()¶
Performs the SSL shutdown handshake, which removes the TLS layer from theunderlying socket, and returns the underlying socket object. This can beused to go from encrypted operation over a connection to unencrypted. Thereturned socket should always be used for further communication with theother side of the connection, rather than the original socket.
- SSLSocket.verify_client_post_handshake()¶
Requests post-handshake authentication (PHA) from a TLS 1.3 client. PHAcan only be initiated for a TLS 1.3 connection from a server-side socket,after the initial TLS handshake and with PHA enabled on both sides, see
SSLContext.post_handshake_auth
.The method does not perform a cert exchange immediately. The server-sidesends a CertificateRequest during the next write event and expects theclient to respond with a certificate on the next read event.
If any precondition isn’t met (e.g. not TLS 1.3, PHA not enabled), an
SSLError
is raised.Σημείωση
Only available with OpenSSL 1.1.1 and TLS 1.3 enabled. Without TLS 1.3support, the method raises
NotImplementedError
.Added in version 3.8.
- SSLSocket.version()¶
Return the actual SSL protocol version negotiated by the connectionas a string, or
None
if no secure connection is established.As of this writing, possible return values include"SSLv2"
,"SSLv3"
,"TLSv1"
,"TLSv1.1"
and"TLSv1.2"
.Recent OpenSSL versions may define more return values.Added in version 3.5.
- SSLSocket.pending()¶
Returns the number of already decrypted bytes available for read, pending onthe connection.
- SSLSocket.context¶
The
SSLContext
object this SSL socket is tied to.Added in version 3.2.
- SSLSocket.server_side¶
A boolean which is
True
for server-side sockets andFalse
forclient-side sockets.Added in version 3.2.
- SSLSocket.server_hostname¶
Hostname of the server:
str
type, orNone
for server-sidesocket or if the hostname was not specified in the constructor.Added in version 3.2.
Άλλαξε στην έκδοση 3.7:The attribute is now always ASCII text. When
server_hostname
isan internationalized domain name (IDN), this attribute now stores theA-label form ("xn--pythn-mua.org"
), rather than the U-label form("pythön.org"
).
- SSLSocket.session¶
The
SSLSession
for this SSL connection. The session is availablefor client and server side sockets after the TLS handshake has beenperformed. For client sockets the session can be set beforedo_handshake()
has been called to reuse a session.Added in version 3.6.
- SSLSocket.session_reused¶
Added in version 3.6.
SSL Contexts¶
Added in version 3.2.
An SSL context holds various data longer-lived than single SSL connections,such as SSL configuration options, certificate(s) and private key(s).It also manages a cache of SSL sessions for server-side sockets, in orderto speed up repeated connections from the same clients.
- classssl.SSLContext(protocol=None)¶
Create a new SSL context. You may passprotocol which must be oneof the
PROTOCOL_*
constants defined in this module. The parameterspecifies which version of the SSL protocol to use. Typically, theserver chooses a particular protocol version, and the client must adaptto the server’s choice. Most of the versions are not interoperablewith the other versions. If not specified, the default isPROTOCOL_TLS
; it provides the most compatibility with otherversions.Here’s a table showing which versions in a client (down the side) can connectto which versions in a server (along the top):
client /server
SSLv2
SSLv3
TLS[3]
TLSv1
TLSv1.1
TLSv1.2
SSLv2
yes
no
no[1]
no
no
no
SSLv3
no
yes
no[2]
no
no
no
TLS (SSLv23)[3]
no[1]
no[2]
yes
yes
yes
yes
TLSv1
no
no
yes
yes
no
no
TLSv1.1
no
no
yes
no
yes
no
TLSv1.2
no
no
yes
no
no
yes
Footnotes
[1](1,2)
[2](1,2)SSLContext
disables SSLv2 withOP_NO_SSLv2
by default.
[3](1,2)SSLContext
disables SSLv3 withOP_NO_SSLv3
by default.TLS 1.3 protocol will be available with
PROTOCOL_TLS
inOpenSSL >= 1.1.1. There is no dedicated PROTOCOL constant for justTLS 1.3.Δείτε επίσης
create_default_context()
lets thessl
module choosesecurity settings for a given purpose.Άλλαξε στην έκδοση 3.6:The context is created with secure default values. The options
OP_NO_COMPRESSION
,OP_CIPHER_SERVER_PREFERENCE
,OP_SINGLE_DH_USE
,OP_SINGLE_ECDH_USE
,OP_NO_SSLv2
,andOP_NO_SSLv3
(except forPROTOCOL_SSLv3
) areset by default. The initial cipher suite list contains onlyHIGH
ciphers, noNULL
ciphers and noMD5
ciphers.Αποσύρθηκε στην έκδοση 3.10:
SSLContext
without protocol argument is deprecated. Thecontext class will either requirePROTOCOL_TLS_CLIENT
orPROTOCOL_TLS_SERVER
protocol in the future.Άλλαξε στην έκδοση 3.10:The default cipher suites now include only secure AES and ChaCha20ciphers with forward secrecy and security level 2. RSA and DH keys withless than 2048 bits and ECC keys with less than 224 bits are prohibited.
PROTOCOL_TLS
,PROTOCOL_TLS_CLIENT
, andPROTOCOL_TLS_SERVER
use TLS 1.2 as minimum TLS version.Σημείωση
SSLContext
only supports limited mutation once it has been usedby a connection. Adding new certificates to the internal trust store isallowed, but changing ciphers, verification settings, or mTLScertificates may result in surprising behavior.Σημείωση
SSLContext
is designed to be shared and used by multipleconnections.Thus, it is thread-safe as long as it is not reconfigured after beingused by a connection.
SSLContext
objects have the following methods and attributes:
- SSLContext.cert_store_stats()¶
Get statistics about quantities of loaded X.509 certificates, count ofX.509 certificates flagged as CA certificates and certificate revocationlists as dictionary.
Example for a context with one CA cert and one other cert:
>>>context.cert_store_stats(){'crl': 0, 'x509_ca': 1, 'x509': 2}
Added in version 3.4.
- SSLContext.load_cert_chain(certfile,keyfile=None,password=None)¶
Load a private key and the corresponding certificate. Thecertfilestring must be the path to a single file in PEM format containing thecertificate as well as any number of CA certificates needed to establishthe certificate’s authenticity. Thekeyfile string, if present, mustpoint to a file containing the private key. Otherwise the privatekey will be taken fromcertfile as well. See the discussion ofCertificates for more information on how the certificateis stored in thecertfile.
Thepassword argument may be a function to call to get the password fordecrypting the private key. It will only be called if the private key isencrypted and a password is necessary. It will be called with no arguments,and it should return a string, bytes, or bytearray. If the return value isa string it will be encoded as UTF-8 before using it to decrypt the key.Alternatively a string, bytes, or bytearray value may be supplied directlyas thepassword argument. It will be ignored if the private key is notencrypted and no password is needed.
If thepassword argument is not specified and a password is required,OpenSSL’s built-in password prompting mechanism will be used tointeractively prompt the user for a password.
An
SSLError
is raised if the private key doesn’tmatch with the certificate.Άλλαξε στην έκδοση 3.3:New optional argumentpassword.
- SSLContext.load_default_certs(purpose=Purpose.SERVER_AUTH)¶
Load a set of default «certification authority» (CA) certificates fromdefault locations. On Windows it loads CA certs from the
CA
andROOT
system stores. On all systems it callsSSLContext.set_default_verify_paths()
. In the future the method mayload CA certificates from other locations, too.Thepurpose flag specifies what kind of CA certificates are loaded. Thedefault settings
Purpose.SERVER_AUTH
loads certificates, that areflagged and trusted for TLS web server authentication (client sidesockets).Purpose.CLIENT_AUTH
loads CA certificates for clientcertificate verification on the server side.Added in version 3.4.
- SSLContext.load_verify_locations(cafile=None,capath=None,cadata=None)¶
Load a set of «certification authority» (CA) certificates used to validateother peers” certificates when
verify_mode
is other thanCERT_NONE
. At least one ofcafile orcapath must be specified.This method can also load certification revocation lists (CRLs) in PEM orDER format. In order to make use of CRLs,
SSLContext.verify_flags
must be configured properly.Thecafile string, if present, is the path to a file of concatenatedCA certificates in PEM format. See the discussion ofCertificates for more information about how to arrange thecertificates in this file.
Thecapath string, if present, isthe path to a directory containing several CA certificates in PEM format,following anOpenSSL specific layout.
Thecadata object, if present, is either an ASCII string of one or morePEM-encoded certificates or abytes-like object of DER-encodedcertificates. Like withcapath extra lines around PEM-encodedcertificates are ignored but at least one certificate must be present.
Άλλαξε στην έκδοση 3.4:New optional argumentcadata
- SSLContext.get_ca_certs(binary_form=False)¶
Get a list of loaded «certification authority» (CA) certificates. If the
binary_form
parameter isFalse
each listentry is a dict like the output ofSSLSocket.getpeercert()
. Otherwisethe method returns a list of DER-encoded certificates. The returned listdoes not contain certificates fromcapath unless a certificate wasrequested and loaded by a SSL connection.Σημείωση
Certificates in a capath directory aren’t loaded unless they havebeen used at least once.
Added in version 3.4.
- SSLContext.get_ciphers()¶
Get a list of enabled ciphers. The list is in order of cipher priority.See
SSLContext.set_ciphers()
.Example:
>>>ctx=ssl.SSLContext(ssl.PROTOCOL_SSLv23)>>>ctx.set_ciphers('ECDHE+AESGCM:!ECDSA')>>>ctx.get_ciphers()[{'aead': True, 'alg_bits': 256, 'auth': 'auth-rsa', 'description': 'ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA ' 'Enc=AESGCM(256) Mac=AEAD', 'digest': None, 'id': 50380848, 'kea': 'kx-ecdhe', 'name': 'ECDHE-RSA-AES256-GCM-SHA384', 'protocol': 'TLSv1.2', 'strength_bits': 256, 'symmetric': 'aes-256-gcm'}, {'aead': True, 'alg_bits': 128, 'auth': 'auth-rsa', 'description': 'ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=RSA ' 'Enc=AESGCM(128) Mac=AEAD', 'digest': None, 'id': 50380847, 'kea': 'kx-ecdhe', 'name': 'ECDHE-RSA-AES128-GCM-SHA256', 'protocol': 'TLSv1.2', 'strength_bits': 128, 'symmetric': 'aes-128-gcm'}]
Added in version 3.6.
- SSLContext.set_default_verify_paths()¶
Load a set of default «certification authority» (CA) certificates froma filesystem path defined when building the OpenSSL library. Unfortunately,there’s no easy way to know whether this method succeeds: no error isreturned if no certificates are to be found. When the OpenSSL library isprovided as part of the operating system, though, it is likely to beconfigured properly.
- SSLContext.set_ciphers(ciphers)¶
Set the available ciphers for sockets created with this context.It should be a string in theOpenSSL cipher list format.If no cipher can be selected (because compile-time options or otherconfiguration forbids use of all the specified ciphers), an
SSLError
will be raised.Σημείωση
when connected, the
SSLSocket.cipher()
method of SSL sockets willgive the currently selected cipher.TLS 1.3 cipher suites cannot be disabled with
set_ciphers()
.
- SSLContext.set_alpn_protocols(protocols)¶
Specify which protocols the socket should advertise during the SSL/TLShandshake. It should be a list of ASCII strings, like
['http/1.1','spdy/2']
, ordered by preference. The selection of a protocol will happenduring the handshake, and will play out according toRFC 7301. After asuccessful handshake, theSSLSocket.selected_alpn_protocol()
method willreturn the agreed-upon protocol.This method will raise
NotImplementedError
ifHAS_ALPN
isFalse
.Added in version 3.5.
- SSLContext.set_npn_protocols(protocols)¶
Specify which protocols the socket should advertise during the SSL/TLShandshake. It should be a list of strings, like
['http/1.1','spdy/2']
,ordered by preference. The selection of a protocol will happen during thehandshake, and will play out according to theApplication Layer Protocol Negotiation. After asuccessful handshake, theSSLSocket.selected_npn_protocol()
method willreturn the agreed-upon protocol.This method will raise
NotImplementedError
ifHAS_NPN
isFalse
.Added in version 3.3.
Αποσύρθηκε στην έκδοση 3.10:NPN has been superseded by ALPN
- SSLContext.sni_callback¶
Register a callback function that will be called after the TLS Client Hellohandshake message has been received by the SSL/TLS server when the TLS clientspecifies a server name indication. The server name indication mechanismis specified inRFC 6066 section 3 - Server Name Indication.
Only one callback can be set per
SSLContext
. Ifsni_callbackis set toNone
then the callback is disabled. Calling this function asubsequent time will disable the previously registered callback.The callback function will be called with threearguments; the first being the
ssl.SSLSocket
, the second is a stringthat represents the server name that the client is intending to communicate(orNone
if the TLS Client Hello does not contain a server name)and the third argument is the originalSSLContext
. The server nameargument is text. For internationalized domain name, the servername is an IDN A-label ("xn--pythn-mua.org"
).A typical use of this callback is to change the
ssl.SSLSocket
’sSSLSocket.context
attribute to a new object of typeSSLContext
representing a certificate chain that matches the servername.Due to the early negotiation phase of the TLS connection, only limitedmethods and attributes are usable like
SSLSocket.selected_alpn_protocol()
andSSLSocket.context
.TheSSLSocket.getpeercert()
,SSLSocket.get_verified_chain()
,SSLSocket.get_unverified_chain()
SSLSocket.cipher()
andSSLSocket.compression()
methods require thatthe TLS connection has progressed beyond the TLS Client Hello and thereforewill not return meaningful values nor can they be called safely.Thesni_callback function must return
None
to allow theTLS negotiation to continue. If a TLS failure is required, a constantALERT_DESCRIPTION_*
can bereturned. Other return values will result in a TLS fatal error withALERT_DESCRIPTION_INTERNAL_ERROR
.If an exception is raised from thesni_callback function the TLSconnection will terminate with a fatal TLS alert message
ALERT_DESCRIPTION_HANDSHAKE_FAILURE
.This method will raise
NotImplementedError
if the OpenSSL libraryhad OPENSSL_NO_TLSEXT defined when it was built.Added in version 3.7.
- SSLContext.set_servername_callback(server_name_callback)¶
This is a legacy API retained for backwards compatibility. When possible,you should use
sni_callback
instead. The givenserver_name_callbackis similar tosni_callback, except that when the server hostname is anIDN-encoded internationalized domain name, theserver_name_callbackreceives a decoded U-label ("pythön.org"
).If there is a decoding error on the server name, the TLS connection willterminate with an
ALERT_DESCRIPTION_INTERNAL_ERROR
fatal TLSalert message to the client.Added in version 3.4.
- SSLContext.load_dh_params(dhfile)¶
Load the key generation parameters for Diffie-Hellman (DH) key exchange.Using DH key exchange improves forward secrecy at the expense ofcomputational resources (both on the server and on the client).Thedhfile parameter should be the path to a file containing DHparameters in PEM format.
This setting doesn’t apply to client sockets. You can also use the
OP_SINGLE_DH_USE
option to further improve security.Added in version 3.3.
- SSLContext.set_ecdh_curve(curve_name)¶
Set the curve name for Elliptic Curve-based Diffie-Hellman (ECDH) keyexchange. ECDH is significantly faster than regular DH while arguablyas secure. Thecurve_name parameter should be a string describinga well-known elliptic curve, for example
prime256v1
for a widelysupported curve.This setting doesn’t apply to client sockets. You can also use the
OP_SINGLE_ECDH_USE
option to further improve security.This method is not available if
HAS_ECDH
isFalse
.Added in version 3.3.
Δείτε επίσης
- SSL/TLS & Perfect Forward Secrecy
Vincent Bernat.
- SSLContext.wrap_socket(sock,server_side=False,do_handshake_on_connect=True,suppress_ragged_eofs=True,server_hostname=None,session=None)¶
Wrap an existing Python socketsock and return an instance of
SSLContext.sslsocket_class
(defaultSSLSocket
). Thereturned SSL socket is tied to the context, its settings and certificates.sock must be aSOCK_STREAM
socket; othersocket types are unsupported.The parameter
server_side
is a boolean which identifies whetherserver-side or client-side behavior is desired from this socket.For client-side sockets, the context construction is lazy; if theunderlying socket isn’t connected yet, the context construction will beperformed after
connect()
is called on the socket. Forserver-side sockets, if the socket has no remote peer, it is assumedto be a listening socket, and the server-side SSL wrapping isautomatically performed on client connections accepted via theaccept()
method. The method may raiseSSLError
.On client connections, the optional parameterserver_hostname specifiesthe hostname of the service which we are connecting to. This allows asingle server to host multiple SSL-based services with distinct certificates,quite similarly to HTTP virtual hosts. Specifyingserver_hostname willraise a
ValueError
ifserver_side is true.The parameter
do_handshake_on_connect
specifies whether to do the SSLhandshake automatically after doing asocket.connect()
, or whether theapplication program will call it explicitly, by invoking theSSLSocket.do_handshake()
method. CallingSSLSocket.do_handshake()
explicitly gives the program control over theblocking behavior of the socket I/O involved in the handshake.The parameter
suppress_ragged_eofs
specifies how theSSLSocket.recv()
method should signal unexpected EOF from the other endof the connection. If specified asTrue
(the default), it returns anormal EOF (an empty bytes object) in response to unexpected EOF errorsraised from the underlying socket; ifFalse
, it will raise theexceptions back to the caller.session, see
session
.To wrap an
SSLSocket
in anotherSSLSocket
, useSSLContext.wrap_bio()
.Άλλαξε στην έκδοση 3.5:Always allow a server_hostname to be passed, even if OpenSSL does nothave SNI.
Άλλαξε στην έκδοση 3.6:session argument was added.
Άλλαξε στην έκδοση 3.7:The method returns an instance of
SSLContext.sslsocket_class
instead of hard-codedSSLSocket
.
- SSLContext.sslsocket_class¶
The return type of
SSLContext.wrap_socket()
, defaults toSSLSocket
. The attribute can be overridden on instance of classin order to return a custom subclass ofSSLSocket
.Added in version 3.7.
- SSLContext.wrap_bio(incoming,outgoing,server_side=False,server_hostname=None,session=None)¶
Wrap the BIO objectsincoming andoutgoing and return an instance of
SSLContext.sslobject_class
(defaultSSLObject
). The SSLroutines will read input data from the incoming BIO and write data to theoutgoing BIO.Theserver_side,server_hostname andsession parameters have thesame meaning as in
SSLContext.wrap_socket()
.Άλλαξε στην έκδοση 3.6:session argument was added.
Άλλαξε στην έκδοση 3.7:The method returns an instance of
SSLContext.sslobject_class
instead of hard-codedSSLObject
.
- SSLContext.sslobject_class¶
The return type of
SSLContext.wrap_bio()
, defaults toSSLObject
. The attribute can be overridden on instance of classin order to return a custom subclass ofSSLObject
.Added in version 3.7.
- SSLContext.session_stats()¶
Get statistics about the SSL sessions created or managed by this context.A dictionary is returned which maps the names of eachpiece of information to theirnumeric values. For example, here is the total number of hits and missesin the session cache since the context was created:
>>>stats=context.session_stats()>>>stats['hits'],stats['misses'](0, 0)
- SSLContext.check_hostname¶
Whether to match the peer cert’s hostname in
SSLSocket.do_handshake()
. The context’sverify_mode
must be set toCERT_OPTIONAL
orCERT_REQUIRED
, and you must passserver_hostname towrap_socket()
in order to match the hostname. Enablinghostname checking automatically setsverify_mode
fromCERT_NONE
toCERT_REQUIRED
. It cannot be set back toCERT_NONE
as long as hostname checking is enabled. ThePROTOCOL_TLS_CLIENT
protocol enables hostname checking by default.With other protocols, hostname checking must be enabled explicitly.Example:
importsocket,sslcontext=ssl.SSLContext(ssl.PROTOCOL_TLSv1_2)context.verify_mode=ssl.CERT_REQUIREDcontext.check_hostname=Truecontext.load_default_certs()s=socket.socket(socket.AF_INET,socket.SOCK_STREAM)ssl_sock=context.wrap_socket(s,server_hostname='www.verisign.com')ssl_sock.connect(('www.verisign.com',443))
Added in version 3.4.
Άλλαξε στην έκδοση 3.7:
verify_mode
is now automatically changedtoCERT_REQUIRED
when hostname checking is enabled andverify_mode
isCERT_NONE
. Previouslythe same operation would have failed with aValueError
.
- SSLContext.keylog_filename¶
Write TLS keys to a keylog file, whenever key material is generated orreceived. The keylog file is designed for debugging purposes only. Thefile format is specified by NSS and used by many traffic analyzers suchas Wireshark. The log file is opened in append-only mode. Writes aresynchronized between threads, but not between processes.
Added in version 3.8.
- SSLContext.maximum_version¶
A
TLSVersion
enum member representing the highest supportedTLS version. The value defaults toTLSVersion.MAXIMUM_SUPPORTED
.The attribute is read-only for protocols other thanPROTOCOL_TLS
,PROTOCOL_TLS_CLIENT
, andPROTOCOL_TLS_SERVER
.The attributes
maximum_version
,minimum_version
andSSLContext.options
all affect the supported SSLand TLS versions of the context. The implementation does not preventinvalid combination. For example a context withOP_NO_TLSv1_2
inoptions
andmaximum_version
set toTLSVersion.TLSv1_2
will not be able to establish a TLS 1.2 connection.Added in version 3.7.
- SSLContext.minimum_version¶
Like
SSLContext.maximum_version
except it is the lowestsupported version orTLSVersion.MINIMUM_SUPPORTED
.Added in version 3.7.
- SSLContext.num_tickets¶
Control the number of TLS 1.3 session tickets of a
PROTOCOL_TLS_SERVER
context. The setting has no impact on TLS1.0 to 1.2 connections.Added in version 3.8.
- SSLContext.options¶
An integer representing the set of SSL options enabled on this context.The default value is
OP_ALL
, but you can specify other optionssuch asOP_NO_SSLv2
by ORing them together.Άλλαξε στην έκδοση 3.6:
SSLContext.options
returnsOptions
flags:>>>ssl.create_default_context().options<Options.OP_ALL|OP_NO_SSLv3|OP_NO_SSLv2|OP_NO_COMPRESSION: 2197947391>
Αποσύρθηκε στην έκδοση 3.7:All
OP_NO_SSL*
andOP_NO_TLS*
options have been deprecated sincePython 3.7. UseSSLContext.minimum_version
andSSLContext.maximum_version
instead.
- SSLContext.post_handshake_auth¶
Enable TLS 1.3 post-handshake client authentication. Post-handshake authis disabled by default and a server can only request a TLS clientcertificate during the initial handshake. When enabled, a server mayrequest a TLS client certificate at any time after the handshake.
When enabled on client-side sockets, the client signals the server thatit supports post-handshake authentication.
When enabled on server-side sockets,
SSLContext.verify_mode
mustbe set toCERT_OPTIONAL
orCERT_REQUIRED
, too. Theactual client cert exchange is delayed untilSSLSocket.verify_client_post_handshake()
is called and some I/O isperformed.Added in version 3.8.
- SSLContext.protocol¶
The protocol version chosen when constructing the context. This attributeis read-only.
- SSLContext.hostname_checks_common_name¶
Whether
check_hostname
falls back to verify the cert’ssubject common name in the absence of a subject alternative nameextension (default: true).Added in version 3.7.
Άλλαξε στην έκδοση 3.10:The flag had no effect with OpenSSL before version 1.1.1l. Python 3.8.9,3.9.3, and 3.10 include workarounds for previous versions.
- SSLContext.security_level¶
An integer representing thesecurity levelfor the context. This attribute is read-only.
Added in version 3.10.
- SSLContext.verify_flags¶
The flags for certificate verification operations. You can set flags like
VERIFY_CRL_CHECK_LEAF
by ORing them together. By default OpenSSLdoes neither require nor verify certificate revocation lists (CRLs).Added in version 3.4.
Άλλαξε στην έκδοση 3.6:
SSLContext.verify_flags
returnsVerifyFlags
flags:>>>ssl.create_default_context().verify_flags<VerifyFlags.VERIFY_X509_TRUSTED_FIRST: 32768>
- SSLContext.verify_mode¶
Whether to try to verify other peers” certificates and how to behaveif verification fails. This attribute must be one of
CERT_NONE
,CERT_OPTIONAL
orCERT_REQUIRED
.Άλλαξε στην έκδοση 3.6:
SSLContext.verify_mode
returnsVerifyMode
enum:>>>ssl.create_default_context().verify_mode<VerifyMode.CERT_REQUIRED: 2>
- SSLContext.set_psk_client_callback(callback)¶
Enables TLS-PSK (pre-shared key) authentication on a client-side connection.
In general, certificate based authentication should be preferred over this method.
The parameter
callback
is a callable object with the signature:defcallback(hint:str|None)->tuple[str|None,bytes]
.Thehint
parameter is an optional identity hint sent by the server.The return value is a tuple in the form (client-identity, psk).Client-identity is an optional string which may be used by the server toselect a corresponding PSK for the client. The string must be less than orequal to256
octets when UTF-8 encoded. PSK is abytes-like object representing the pre-shared key. Return a zerolength PSK to reject the connection.Setting
callback
toNone
removes any existing callback.Σημείωση
When using TLS 1.3:
the
hint
parameter is alwaysNone
.client-identity must be a non-empty string.
Example usage:
context=ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)context.check_hostname=Falsecontext.verify_mode=ssl.CERT_NONEcontext.maximum_version=ssl.TLSVersion.TLSv1_2context.set_ciphers('PSK')# A simple lambda:psk=bytes.fromhex('c0ffee')context.set_psk_client_callback(lambdahint:(None,psk))# A table using the hint from the server:psk_table={'ServerId_1':bytes.fromhex('c0ffee'),'ServerId_2':bytes.fromhex('facade')}defcallback(hint):return'ClientId_1',psk_table.get(hint,b'')context.set_psk_client_callback(callback)
This method will raise
NotImplementedError
ifHAS_PSK
isFalse
.Added in version 3.13.
- SSLContext.set_psk_server_callback(callback,identity_hint=None)¶
Enables TLS-PSK (pre-shared key) authentication on a server-side connection.
In general, certificate based authentication should be preferred over this method.
The parameter
callback
is a callable object with the signature:defcallback(identity:str|None)->bytes
.Theidentity
parameter is an optional identity sent by the client which canbe used to select a corresponding PSK.The return value is abytes-like object representing the pre-shared key.Return a zero length PSK to reject the connection.Setting
callback
toNone
removes any existing callback.The parameter
identity_hint
is an optional identity hint string sent tothe client. The string must be less than or equal to256
octets whenUTF-8 encoded.Σημείωση
When using TLS 1.3 the
identity_hint
parameter is not sent to the client.Example usage:
context=ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)context.maximum_version=ssl.TLSVersion.TLSv1_2context.set_ciphers('PSK')# A simple lambda:psk=bytes.fromhex('c0ffee')context.set_psk_server_callback(lambdaidentity:psk)# A table using the identity of the client:psk_table={'ClientId_1':bytes.fromhex('c0ffee'),'ClientId_2':bytes.fromhex('facade')}defcallback(identity):returnpsk_table.get(identity,b'')context.set_psk_server_callback(callback,'ServerId_1')
This method will raise
NotImplementedError
ifHAS_PSK
isFalse
.Added in version 3.13.
Certificates¶
Certificates in general are part of a public-key / private-key system. In thissystem, eachprincipal, (which may be a machine, or a person, or anorganization) is assigned a unique two-part encryption key. One part of the keyis public, and is called thepublic key; the other part is kept secret, and iscalled theprivate key. The two parts are related, in that if you encrypt amessage with one of the parts, you can decrypt it with the other part, andonly with the other part.
A certificate contains information about two principals. It contains the nameof asubject, and the subject’s public key. It also contains a statement by asecond principal, theissuer, that the subject is who they claim to be, andthat this is indeed the subject’s public key. The issuer’s statement is signedwith the issuer’s private key, which only the issuer knows. However, anyone canverify the issuer’s statement by finding the issuer’s public key, decrypting thestatement with it, and comparing it to the other information in the certificate.The certificate also contains information about the time period over which it isvalid. This is expressed as two fields, called «notBefore» and «notAfter».
In the Python use of certificates, a client or server can use a certificate toprove who they are. The other side of a network connection can also be requiredto produce a certificate, and that certificate can be validated to thesatisfaction of the client or server that requires such validation. Theconnection attempt can be set to raise an exception if the validation fails.Validation is done automatically, by the underlying OpenSSL framework; theapplication need not concern itself with its mechanics. But the applicationdoes usually need to provide sets of certificates to allow this process to takeplace.
Python uses files to contain certificates. They should be formatted as «PEM»(seeRFC 1422), which is a base-64 encoded form wrapped with a header lineand a footer line:
-----BEGINCERTIFICATE-----...(certificateinbase64PEMencoding)...-----ENDCERTIFICATE-----
Certificate chains¶
The Python files which contain certificates can contain a sequence ofcertificates, sometimes called acertificate chain. This chain should startwith the specific certificate for the principal who «is» the client or server,and then the certificate for the issuer of that certificate, and then thecertificate for the issuer ofthat certificate, and so on up the chain tillyou get to a certificate which isself-signed, that is, a certificate whichhas the same subject and issuer, sometimes called aroot certificate. Thecertificates should just be concatenated together in the certificate file. Forexample, suppose we had a three certificate chain, from our server certificateto the certificate of the certification authority that signed our servercertificate, to the root certificate of the agency which issued thecertification authority’s certificate:
-----BEGINCERTIFICATE-----...(certificateforyourserver)...-----ENDCERTIFICATE----------BEGINCERTIFICATE-----...(thecertificatefortheCA)...-----ENDCERTIFICATE----------BEGINCERTIFICATE-----...(therootcertificatefortheCA's issuer)...-----ENDCERTIFICATE-----
CA certificates¶
If you are going to require validation of the other side of the connection’scertificate, you need to provide a «CA certs» file, filled with the certificatechains for each issuer you are willing to trust. Again, this file just containsthese chains concatenated together. For validation, Python will use the firstchain it finds in the file which matches. The platform’s certificates file canbe used by callingSSLContext.load_default_certs()
, this is doneautomatically withcreate_default_context()
.
Combined key and certificate¶
Often the private key is stored in the same file as the certificate; in thiscase, only thecertfile
parameter toSSLContext.load_cert_chain()
needs to be passed. If the private key is storedwith the certificate, it should come before the first certificate inthe certificate chain:
-----BEGINRSAPRIVATEKEY-----...(privatekeyinbase64encoding)...-----ENDRSAPRIVATEKEY----------BEGINCERTIFICATE-----...(certificateinbase64PEMencoding)...-----ENDCERTIFICATE-----
Self-signed certificates¶
If you are going to create a server that provides SSL-encrypted connectionservices, you will need to acquire a certificate for that service. There aremany ways of acquiring appropriate certificates, such as buying one from acertification authority. Another common practice is to generate a self-signedcertificate. The simplest way to do this is with the OpenSSL package, usingsomething like the following:
%opensslreq-new-x509-days365-nodes-outcert.pem-keyoutcert.pemGeneratinga1024bitRSAprivatekey.......++++++.............................++++++writingnewprivatekeyto'cert.pem'-----Youareabouttobeaskedtoenterinformationthatwillbeincorporatedintoyourcertificaterequest.WhatyouareabouttoenteriswhatiscalledaDistinguishedNameoraDN.TherearequiteafewfieldsbutyoucanleavesomeblankForsomefieldstherewillbeadefaultvalue,Ifyouenter'.',thefieldwillbeleftblank.-----CountryName(2lettercode)[AU]:USStateorProvinceName(fullname)[Some-State]:MyStateLocalityName(eg,city)[]:SomeCityOrganizationName(eg,company)[InternetWidgitsPtyLtd]:MyOrganization,Inc.OrganizationalUnitName(eg,section)[]:MyGroupCommonName(eg,YOURname)[]:myserver.mygroup.myorganization.comEmailAddress[]:ops@myserver.mygroup.myorganization.com%
The disadvantage of a self-signed certificate is that it is its own rootcertificate, and no one else will have it in their cache of known (and trusted)root certificates.
Examples¶
Testing for SSL support¶
To test for the presence of SSL support in a Python installation, user codeshould use the following idiom:
try:importsslexceptImportError:passelse:...# do something that requires SSL support
Client-side operation¶
This example creates a SSL context with the recommended security settingsfor client sockets, including automatic certificate verification:
>>>context=ssl.create_default_context()
If you prefer to tune security settings yourself, you might createa context from scratch (but beware that you might not get the settingsright):
>>>context=ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)>>>context.load_verify_locations("/etc/ssl/certs/ca-bundle.crt")
(this snippet assumes your operating system places a bundle of all CAcertificates in/etc/ssl/certs/ca-bundle.crt
; if not, you’ll get anerror and have to adjust the location)
ThePROTOCOL_TLS_CLIENT
protocol configures the context for certvalidation and hostname verification.verify_mode
isset toCERT_REQUIRED
andcheck_hostname
is settoTrue
. All other protocols create SSL contexts with insecure defaults.
When you use the context to connect to a server,CERT_REQUIRED
andcheck_hostname
validate the server certificate: itensures that the server certificate was signed with one of the CAcertificates, checks the signature for correctness, and verifies otherproperties like validity and identity of the hostname:
>>>conn=context.wrap_socket(socket.socket(socket.AF_INET),...server_hostname="www.python.org")>>>conn.connect(("www.python.org",443))
You may then fetch the certificate:
>>>cert=conn.getpeercert()
Visual inspection shows that the certificate does identify the desired service(that is, the HTTPS hostwww.python.org
):
>>>pprint.pprint(cert){'OCSP': ('http://ocsp.digicert.com',), 'caIssuers': ('http://cacerts.digicert.com/DigiCertSHA2ExtendedValidationServerCA.crt',), 'crlDistributionPoints': ('http://crl3.digicert.com/sha2-ev-server-g1.crl', 'http://crl4.digicert.com/sha2-ev-server-g1.crl'), 'issuer': ((('countryName', 'US'),), (('organizationName', 'DigiCert Inc'),), (('organizationalUnitName', 'www.digicert.com'),), (('commonName', 'DigiCert SHA2 Extended Validation Server CA'),)), 'notAfter': 'Sep 9 12:00:00 2016 GMT', 'notBefore': 'Sep 5 00:00:00 2014 GMT', 'serialNumber': '01BB6F00122B177F36CAB49CEA8B6B26', 'subject': ((('businessCategory', 'Private Organization'),), (('1.3.6.1.4.1.311.60.2.1.3', 'US'),), (('1.3.6.1.4.1.311.60.2.1.2', 'Delaware'),), (('serialNumber', '3359300'),), (('streetAddress', '16 Allen Rd'),), (('postalCode', '03894-4801'),), (('countryName', 'US'),), (('stateOrProvinceName', 'NH'),), (('localityName', 'Wolfeboro'),), (('organizationName', 'Python Software Foundation'),), (('commonName', 'www.python.org'),)), 'subjectAltName': (('DNS', 'www.python.org'), ('DNS', 'python.org'), ('DNS', 'pypi.org'), ('DNS', 'docs.python.org'), ('DNS', 'testpypi.org'), ('DNS', 'bugs.python.org'), ('DNS', 'wiki.python.org'), ('DNS', 'hg.python.org'), ('DNS', 'mail.python.org'), ('DNS', 'packaging.python.org'), ('DNS', 'pythonhosted.org'), ('DNS', 'www.pythonhosted.org'), ('DNS', 'test.pythonhosted.org'), ('DNS', 'us.pycon.org'), ('DNS', 'id.python.org')), 'version': 3}
Now the SSL channel is established and the certificate verified, you canproceed to talk with the server:
>>>conn.sendall(b"HEAD / HTTP/1.0\r\nHost: linuxfr.org\r\n\r\n")>>>pprint.pprint(conn.recv(1024).split(b"\r\n"))[b'HTTP/1.1 200 OK', b'Date: Sat, 18 Oct 2014 18:27:20 GMT', b'Server: nginx', b'Content-Type: text/html; charset=utf-8', b'X-Frame-Options: SAMEORIGIN', b'Content-Length: 45679', b'Accept-Ranges: bytes', b'Via: 1.1 varnish', b'Age: 2188', b'X-Served-By: cache-lcy1134-LCY', b'X-Cache: HIT', b'X-Cache-Hits: 11', b'Vary: Cookie', b'Strict-Transport-Security: max-age=63072000; includeSubDomains', b'Connection: close', b'', b'']
See the discussion ofSecurity considerations below.
Server-side operation¶
For server operation, typically you’ll need to have a server certificate, andprivate key, each in a file. You’ll first create a context holding the keyand the certificate, so that clients can check your authenticity. Thenyou’ll open a socket, bind it to a port, calllisten()
on it, and startwaiting for clients to connect:
importsocket,sslcontext=ssl.create_default_context(ssl.Purpose.CLIENT_AUTH)context.load_cert_chain(certfile="mycertfile",keyfile="mykeyfile")bindsocket=socket.socket()bindsocket.bind(('myaddr.example.com',10023))bindsocket.listen(5)
When a client connects, you’ll callaccept()
on the socket to get thenew socket from the other end, and use the context’sSSLContext.wrap_socket()
method to create a server-side SSL socket for the connection:
whileTrue:newsocket,fromaddr=bindsocket.accept()connstream=context.wrap_socket(newsocket,server_side=True)try:deal_with_client(connstream)finally:connstream.shutdown(socket.SHUT_RDWR)connstream.close()
Then you’ll read data from theconnstream
and do something with it till youare finished with the client (or the client is finished with you):
defdeal_with_client(connstream):data=connstream.recv(1024)# empty data means the client is finished with uswhiledata:ifnotdo_something(connstream,data):# we'll assume do_something returns False# when we're finished with clientbreakdata=connstream.recv(1024)# finished with client
And go back to listening for new client connections (of course, a real serverwould probably handle each client connection in a separate thread, or putthe sockets innon-blocking mode and use an event loop).
Notes on non-blocking sockets¶
SSL sockets behave slightly different than regular sockets innon-blocking mode. When working with non-blocking sockets, there arethus several things you need to be aware of:
Most
SSLSocket
methods will raise eitherSSLWantWriteError
orSSLWantReadError
instead ofBlockingIOError
if an I/O operation wouldblock.SSLWantReadError
will be raised if a read operation onthe underlying socket is necessary, andSSLWantWriteError
fora write operation on the underlying socket. Note that attempts towrite to an SSL socket may requirereading from the underlyingsocket first, and attempts toread from the SSL socket may requirea priorwrite to the underlying socket.Άλλαξε στην έκδοση 3.5:In earlier Python versions, the
SSLSocket.send()
methodreturned zero instead of raisingSSLWantWriteError
orSSLWantReadError
.Calling
select()
tells you that the OS-level socket can beread from (or written to), but it does not imply that there is sufficientdata at the upper SSL layer. For example, only part of an SSL frame mighthave arrived. Therefore, you must be ready to handleSSLSocket.recv()
andSSLSocket.send()
failures, and retry after another call toselect()
.Conversely, since the SSL layer has its own framing, a SSL socket maystill have data available for reading without
select()
being aware of it. Therefore, you should first callSSLSocket.recv()
to drain any potentially available data, and thenonly block on aselect()
call if still necessary.(of course, similar provisions apply when using other primitives such as
poll()
, or those in theselectors
module)The SSL handshake itself will be non-blocking: the
SSLSocket.do_handshake()
method has to be retried until it returnssuccessfully. Here is a synopsis usingselect()
to wait forthe socket’s readiness:whileTrue:try:sock.do_handshake()breakexceptssl.SSLWantReadError:select.select([sock],[],[])exceptssl.SSLWantWriteError:select.select([],[sock],[])
Δείτε επίσης
Theasyncio
module supportsnon-blocking SSL sockets and provides a higher levelStreams API.It polls for events using theselectors
module andhandlesSSLWantWriteError
,SSLWantReadError
andBlockingIOError
exceptions. It runs the SSL handshake asynchronouslyas well.
Memory BIO Support¶
Added in version 3.5.
Ever since the SSL module was introduced in Python 2.6, theSSLSocket
class has provided two related but distinct areas of functionality:
SSL protocol handling
Network IO
The network IO API is identical to that provided bysocket.socket
,from whichSSLSocket
also inherits. This allows an SSL socket to beused as a drop-in replacement for a regular socket, making it very easy to addSSL support to an existing application.
Combining SSL protocol handling and network IO usually works well, but thereare some cases where it doesn’t. An example is async IO frameworks that want touse a different IO multiplexing model than the «select/poll on a filedescriptor» (readiness based) model that is assumed bysocket.socket
and by the internal OpenSSL socket IO routines. This is mostly relevant forplatforms like Windows where this model is not efficient. For this purpose, areduced scope variant ofSSLSocket
calledSSLObject
isprovided.
- classssl.SSLObject¶
A reduced-scope variant of
SSLSocket
representing an SSL protocolinstance that does not contain any network IO methods. This class istypically used by framework authors that want to implement asynchronous IOfor SSL through memory buffers.This class implements an interface on top of a low-level SSL object asimplemented by OpenSSL. This object captures the state of an SSL connectionbut does not provide any network IO itself. IO needs to be performed throughseparate «BIO» objects which are OpenSSL’s IO abstraction layer.
This class has no public constructor. An
SSLObject
instancemust be created using thewrap_bio()
method. Thismethod will create theSSLObject
instance and bind it to apair of BIOs. Theincoming BIO is used to pass data from Python to theSSL protocol instance, while theoutgoing BIO is used to pass data theother way around.The following methods are available:
When compared to
SSLSocket
, this object lacks the followingfeatures:Any form of network IO;
recv()
andsend()
read and write only tothe underlyingMemoryBIO
buffers.There is nodo_handshake_on_connect machinery. You must always manuallycall
do_handshake()
to start the handshake.There is no handling ofsuppress_ragged_eofs. All end-of-file conditionsthat are in violation of the protocol are reported via the
SSLEOFError
exception.The method
unwrap()
call does not return anything,unlike for an SSL socket where it returns the underlying socket.Theserver_name_callback callback passed to
SSLContext.set_servername_callback()
will get anSSLObject
instance instead of aSSLSocket
instance as its first parameter.
Some notes related to the use of
SSLObject
:All IO on an
SSLObject
isnon-blocking.This means that for exampleread()
will raise anSSLWantReadError
if it needs more data than the incoming BIO hasavailable.
Άλλαξε στην έκδοση 3.7:
SSLObject
instances must be created withwrap_bio()
. In earlier versions, it was possible tocreate instances directly. This was never documented or officiallysupported.
An SSLObject communicates with the outside world using memory buffers. TheclassMemoryBIO
provides a memory buffer that can be used for thispurpose. It wraps an OpenSSL memory BIO (Basic IO) object:
- classssl.MemoryBIO¶
A memory buffer that can be used to pass data between Python and an SSLprotocol instance.
- pending¶
Return the number of bytes currently in the memory buffer.
- eof¶
A boolean indicating whether the memory BIO is current at the end-of-fileposition.
- read(n=-1)¶
Read up ton bytes from the memory buffer. Ifn is not specified ornegative, all bytes are returned.
- write(buf)¶
Write the bytes frombuf to the memory BIO. Thebuf argument must be anobject supporting the buffer protocol.
The return value is the number of bytes written, which is always equal tothe length ofbuf.
SSL session¶
Added in version 3.6.
Security considerations¶
Best defaults¶
Forclient use, if you don’t have any special requirements for yoursecurity policy, it is highly recommended that you use thecreate_default_context()
function to create your SSL context.It will load the system’s trusted CA certificates, enable certificatevalidation and hostname checking, and try to choose reasonably secureprotocol and cipher settings.
For example, here is how you would use thesmtplib.SMTP
class tocreate a trusted, secure connection to a SMTP server:
>>>importssl,smtplib>>>smtp=smtplib.SMTP("mail.python.org",port=587)>>>context=ssl.create_default_context()>>>smtp.starttls(context=context)(220, b'2.0.0 Ready to start TLS')
If a client certificate is needed for the connection, it can be added withSSLContext.load_cert_chain()
.
By contrast, if you create the SSL context by calling theSSLContext
constructor yourself, it will not have certificate validation nor hostnamechecking enabled by default. If you do so, please read the paragraphs belowto achieve a good security level.
Manual settings¶
Verifying certificates¶
When calling theSSLContext
constructor directly,CERT_NONE
is the default. Since it does not authenticate the otherpeer, it can be insecure, especially in client mode where most of the time youwould like to ensure the authenticity of the server you’re talking to.Therefore, when in client mode, it is highly recommended to useCERT_REQUIRED
. However, it is in itself not sufficient; you alsohave to check that the server certificate, which can be obtained by callingSSLSocket.getpeercert()
, matches the desired service. For manyprotocols and applications, the service can be identified by the hostname.This common check is automatically performed whenSSLContext.check_hostname
is enabled.
Άλλαξε στην έκδοση 3.7:Hostname matchings is now performed by OpenSSL. Python no longer usesmatch_hostname()
.
In server mode, if you want to authenticate your clients using the SSL layer(rather than using a higher-level authentication mechanism), you’ll also haveto specifyCERT_REQUIRED
and similarly check the client certificate.
Protocol versions¶
SSL versions 2 and 3 are considered insecure and are therefore dangerous touse. If you want maximum compatibility between clients and servers, it isrecommended to usePROTOCOL_TLS_CLIENT
orPROTOCOL_TLS_SERVER
as the protocol version. SSLv2 and SSLv3 aredisabled by default.
>>>client_context=ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)>>>client_context.minimum_version=ssl.TLSVersion.TLSv1_3>>>client_context.maximum_version=ssl.TLSVersion.TLSv1_3
The SSL context created above will only allow TLSv1.3 and later (ifsupported by your system) connections to a server.PROTOCOL_TLS_CLIENT
implies certificate validation and hostname checks by default. You have toload certificates into the context.
Cipher selection¶
If you have advanced security requirements, fine-tuning of the ciphersenabled when negotiating a SSL session is possible through theSSLContext.set_ciphers()
method. Starting from Python 3.2.3, thessl module disables certain weak ciphers by default, but you may wantto further restrict the cipher choice. Be sure to read OpenSSL’s documentationabout thecipher list format.If you want to check which ciphers are enabled by a given cipher list, useSSLContext.get_ciphers()
or theopensslciphers
command on yoursystem.
Multi-processing¶
If using this module as part of a multi-processed application (using,for example themultiprocessing
orconcurrent.futures
modules),be aware that OpenSSL’s internal random number generator does not properlyhandle forked processes. Applications must change the PRNG state of theparent process if they use any SSL feature withos.fork()
. Anysuccessful call ofRAND_add()
orRAND_bytes()
issufficient.
TLS 1.3¶
Added in version 3.7.
The TLS 1.3 protocol behaves slightly differently than previous versionof TLS/SSL. Some new TLS 1.3 features are not yet available.
TLS 1.3 uses a disjunct set of cipher suites. All AES-GCM andChaCha20 cipher suites are enabled by default. The method
SSLContext.set_ciphers()
cannot enable or disable any TLS 1.3ciphers yet, butSSLContext.get_ciphers()
returns them.Session tickets are no longer sent as part of the initial handshake andare handled differently.
SSLSocket.session
andSSLSession
are not compatible with TLS 1.3.Client-side certificates are also no longer verified during the initialhandshake. A server can request a certificate at any time. Clientsprocess certificate requests while they send or receive application datafrom the server.
TLS 1.3 features like early data, deferred TLS client cert request,signature algorithm configuration, and rekeying are not supported yet.
Δείτε επίσης
- Class
socket.socket
Documentation of underlying
socket
class- SSL/TLS Strong Encryption: An Introduction
Intro from the Apache HTTP Server documentation
- RFC 1422: Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management
Steve Kent
- RFC 4086: Randomness Requirements for Security
Donald E., Jeffrey I. Schiller
- RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
D. Cooper
- RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
T. Dierks et. al.
- RFC 6066: Transport Layer Security (TLS) Extensions
D. Eastlake
- IANA TLS: Transport Layer Security (TLS) Parameters
IANA
- RFC 7525: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
IETF
- Mozilla’s Server Side TLS recommendations
Mozilla