python-docs-fr/library/ssl.po

2572 lines
90 KiB
Plaintext
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2016, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.5\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-10-30 10:42+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../Doc/library/ssl.rst:2
msgid ":mod:`ssl` --- TLS/SSL wrapper for socket objects"
msgstr ":mod:`ssl` — Emballage TLS/SSL pour les objets connecteurs"
#: ../Doc/library/ssl.rst:10
msgid "**Source code:** :source:`Lib/ssl.py`"
msgstr "**Code source :** :source:`Lib/ssl.py`"
#: ../Doc/library/ssl.rst:18
msgid ""
"This module provides access to Transport Layer Security (often known as "
"\"Secure Sockets Layer\") encryption and peer authentication facilities for "
"network sockets, both client-side and server-side. This module uses the "
"OpenSSL library. It is available on all modern Unix systems, Windows, Mac OS "
"X, and probably additional platforms, as long as OpenSSL is installed on "
"that platform."
msgstr ""
"Ce module fournit un accès aux fonctions de chiffrement et "
"d'authentification entre pairs : « *Transport Layer Security* » (souvent "
"appelé « *Secure Sockets Layer* ») pour les connecteurs réseau, côté client "
"et côté serveur. Ce module utilise la bibliothèque OpenSSL. Il est "
"disponible sur tous les systèmes Unix modernes, Windows, Mac OS X et "
"probablement sur d'autres plates-formes, à condition qu'OpenSSL soit "
"installé sur cette plate-forme."
#: ../Doc/library/ssl.rst:26
msgid ""
"Some behavior may be platform dependent, since calls are made to the "
"operating system socket APIs. The installed version of OpenSSL may also "
"cause variations in behavior. For example, TLSv1.1 and TLSv1.2 come with "
"openssl version 1.0.1."
msgstr ""
"Certains comportements peuvent dépendre de la plate-forme, car des appels "
"sont passés aux API de connexions du système d'exploitation. La version "
"installée de OpenSSL peut également entraîner des variations de "
"comportement. Par exemple, TLSv1.1 et TLSv1.2 sont livrés avec la version "
"1.0.1 de OpenSSL."
#: ../Doc/library/ssl.rst:32
msgid ""
"Don't use this module without reading the :ref:`ssl-security`. Doing so may "
"lead to a false sense of security, as the default settings of the ssl module "
"are not necessarily appropriate for your application."
msgstr ""
"Nutilisez pas ce module sans lire :ref:`ssl-security`. Cela pourrait créer "
"un faux sentiment de sécurité, car les paramètres par défaut du module *ssl* "
"ne sont pas nécessairement appropriés pour votre application."
#: ../Doc/library/ssl.rst:37
msgid ""
"This section documents the objects and functions in the ``ssl`` module; for "
"more general information about TLS, SSL, and certificates, the reader is "
"referred to the documents in the \"See Also\" section at the bottom."
msgstr ""
"Cette section documente les objets et les fonctions du module ``ssl``. Pour "
"des informations plus générales sur TLS, SSL et les certificats, le lecteur "
"est prié de se référer aux documents de la section « Voir Aussi » au bas de "
"cette page."
#: ../Doc/library/ssl.rst:41
msgid ""
"This module provides a class, :class:`ssl.SSLSocket`, which is derived from "
"the :class:`socket.socket` type, and provides a socket-like wrapper that "
"also encrypts and decrypts the data going over the socket with SSL. It "
"supports additional methods such as :meth:`getpeercert`, which retrieves the "
"certificate of the other side of the connection, and :meth:`cipher`,which "
"retrieves the cipher being used for the secure connection."
msgstr ""
#: ../Doc/library/ssl.rst:48
msgid ""
"For more sophisticated applications, the :class:`ssl.SSLContext` class helps "
"manage settings and certificates, which can then be inherited by SSL sockets "
"created through the :meth:`SSLContext.wrap_socket` method."
msgstr ""
"Pour les applications plus sophistiquées, la classe :class:`ssl.SSLContext` "
"facilite la gestion des paramètres et des certificats, qui peuvent ensuite "
"être hérités par les connecteurs SSL créés via la méthode :meth:`SSLContext."
"wrap_socket`."
#: ../Doc/library/ssl.rst:54
msgid "Functions, Constants, and Exceptions"
msgstr "Fonctions, constantes et exceptions"
#: ../Doc/library/ssl.rst:58
msgid ""
"Raised to signal an error from the underlying SSL implementation (currently "
"provided by the OpenSSL library). This signifies some problem in the higher-"
"level encryption and authentication layer that's superimposed on the "
"underlying network connection. This error is a subtype of :exc:`OSError`. "
"The error code and message of :exc:`SSLError` instances are provided by the "
"OpenSSL library."
msgstr ""
"Levée pour signaler une erreur de l'implémentation SSL sous-jacente "
"(actuellement fournie par la bibliothèque OpenSSL). Cela signifie qu'un "
"problème est apparu dans la couche d'authentification et de chiffrement de "
"niveau supérieur qui s'appuie sur la connexion réseau sous-jacente. Cette "
"erreur est un sous-type de :exc:`OSError`. Le code d'erreur et le message "
"des instances de :exc:`SSLError` sont fournis par la bibliothèque OpenSSL."
#: ../Doc/library/ssl.rst:65
msgid ":exc:`SSLError` used to be a subtype of :exc:`socket.error`."
msgstr ":exc:`SSLError` était un sous-type de :exc:`socket.error`."
#: ../Doc/library/ssl.rst:70
msgid ""
"A string mnemonic designating the OpenSSL submodule in which the error "
"occurred, such as ``SSL``, ``PEM`` or ``X509``. The range of possible "
"values depends on the OpenSSL version."
msgstr ""
"Une chaîne de caractères mnémonique désignant le sous-module OpenSSL dans "
"lequel l'erreur s'est produite, telle que ``SSL``, ``PEM`` ou ``X509``. "
"L'étendue des valeurs possibles dépend de la version d'OpenSSL."
#: ../Doc/library/ssl.rst:78
msgid ""
"A string mnemonic designating the reason this error occurred, for example "
"``CERTIFICATE_VERIFY_FAILED``. The range of possible values depends on the "
"OpenSSL version."
msgstr ""
#: ../Doc/library/ssl.rst:86
msgid ""
"A subclass of :exc:`SSLError` raised when trying to read or write and the "
"SSL connection has been closed cleanly. Note that this doesn't mean that "
"the underlying transport (read TCP) has been closed."
msgstr ""
#: ../Doc/library/ssl.rst:94
msgid ""
"A subclass of :exc:`SSLError` raised by a :ref:`non-blocking SSL socket <ssl-"
"nonblocking>` when trying to read or write data, but more data needs to be "
"received on the underlying TCP transport before the request can be fulfilled."
msgstr ""
"Sous-classe de :exc:`SSLError` levée par un connecteur :ref:`SSL non "
"bloquant <ssl-nonblocking>` lors d'une tentative de lecture ou d'écriture de "
"données, alors que davantage de données doivent être reçues sur la couche "
"TCP sous-jacente avant que la demande puisse être satisfaite."
#: ../Doc/library/ssl.rst:103
msgid ""
"A subclass of :exc:`SSLError` raised by a :ref:`non-blocking SSL socket <ssl-"
"nonblocking>` when trying to read or write data, but more data needs to be "
"sent on the underlying TCP transport before the request can be fulfilled."
msgstr ""
#: ../Doc/library/ssl.rst:112
msgid ""
"A subclass of :exc:`SSLError` raised when a system error was encountered "
"while trying to fulfill an operation on a SSL socket. Unfortunately, there "
"is no easy way to inspect the original errno number."
msgstr ""
#: ../Doc/library/ssl.rst:120
msgid ""
"A subclass of :exc:`SSLError` raised when the SSL connection has been "
"terminated abruptly. Generally, you shouldn't try to reuse the underlying "
"transport when this error is encountered."
msgstr ""
#: ../Doc/library/ssl.rst:128
msgid ""
"Raised to signal an error with a certificate (such as mismatching "
"hostname). Certificate errors detected by OpenSSL, though, raise an :exc:"
"`SSLError`."
msgstr ""
#: ../Doc/library/ssl.rst:134
msgid "Socket creation"
msgstr "Création de connecteurs"
#: ../Doc/library/ssl.rst:136
msgid ""
"The following function allows for standalone socket creation. Starting from "
"Python 3.2, it can be more flexible to use :meth:`SSLContext.wrap_socket` "
"instead."
msgstr ""
#: ../Doc/library/ssl.rst:142
msgid ""
"Takes an instance ``sock`` of :class:`socket.socket`, and returns an "
"instance of :class:`ssl.SSLSocket`, a subtype of :class:`socket.socket`, "
"which wraps the underlying socket in an SSL context. ``sock`` must be a :"
"data:`~socket.SOCK_STREAM` socket; other socket types are unsupported."
msgstr ""
#: ../Doc/library/ssl.rst:147
msgid ""
"For client-side sockets, the context construction is lazy; if the underlying "
"socket isn't connected yet, the context construction will be performed "
"after :meth:`connect` is called on the socket. For server-side sockets, if "
"the socket has no remote peer, it is assumed to be a listening socket, and "
"the server-side SSL wrapping is automatically performed on client "
"connections accepted via the :meth:`accept` method. :func:`wrap_socket` may "
"raise :exc:`SSLError`."
msgstr ""
#: ../Doc/library/ssl.rst:155
msgid ""
"The ``keyfile`` and ``certfile`` parameters specify optional files which "
"contain a certificate to be used to identify the local side of the "
"connection. See the discussion of :ref:`ssl-certificates` for more "
"information on how the certificate is stored in the ``certfile``."
msgstr ""
#: ../Doc/library/ssl.rst:160
msgid ""
"The parameter ``server_side`` is a boolean which identifies whether server-"
"side or client-side behavior is desired from this socket."
msgstr ""
#: ../Doc/library/ssl.rst:163
msgid ""
"The parameter ``cert_reqs`` specifies whether a certificate is required from "
"the other side of the connection, and whether it will be validated if "
"provided. It must be one of the three values :const:`CERT_NONE` "
"(certificates ignored), :const:`CERT_OPTIONAL` (not required, but validated "
"if provided), or :const:`CERT_REQUIRED` (required and validated). If the "
"value of this parameter is not :const:`CERT_NONE`, then the ``ca_certs`` "
"parameter must point to a file of CA certificates."
msgstr ""
#: ../Doc/library/ssl.rst:171
msgid ""
"The ``ca_certs`` file contains a set of concatenated \"certification "
"authority\" certificates, which are used to validate certificates passed "
"from the other end of the connection. See the discussion of :ref:`ssl-"
"certificates` for more information about how to arrange the certificates in "
"this file."
msgstr ""
#: ../Doc/library/ssl.rst:177
msgid ""
"The parameter ``ssl_version`` specifies which version of the SSL protocol to "
"use. Typically, the server chooses a particular protocol version, and the "
"client must adapt to the server's choice. Most of the versions are not "
"interoperable with the other versions. If not specified, the default is :"
"data:`PROTOCOL_TLS`; it provides the most compatibility with other versions."
msgstr ""
#: ../Doc/library/ssl.rst:184
msgid ""
"Here's a table showing which versions in a client (down the side) can "
"connect to which versions in a server (along the top):"
msgstr ""
#: ../Doc/library/ssl.rst:190
msgid "*client* / **server**"
msgstr ""
#: ../Doc/library/ssl.rst:190
msgid "**SSLv2**"
msgstr "**SSLv2**"
#: ../Doc/library/ssl.rst:190
msgid "**SSLv3**"
msgstr "**SSLv3**"
#: ../Doc/library/ssl.rst:190
msgid "**TLS**"
msgstr ""
#: ../Doc/library/ssl.rst:190
msgid "**TLSv1**"
msgstr "**TLSv1**"
#: ../Doc/library/ssl.rst:190
msgid "**TLSv1.1**"
msgstr "**TLSv1.1**"
#: ../Doc/library/ssl.rst:190
msgid "**TLSv1.2**"
msgstr "**TLSv1.2**"
#: ../Doc/library/ssl.rst:192
msgid "*SSLv2*"
msgstr "*SSLv2*"
#: ../Doc/library/ssl.rst:192 ../Doc/library/ssl.rst:193
#: ../Doc/library/ssl.rst:194 ../Doc/library/ssl.rst:195
#: ../Doc/library/ssl.rst:196 ../Doc/library/ssl.rst:197
msgid "yes"
msgstr "oui"
#: ../Doc/library/ssl.rst:192 ../Doc/library/ssl.rst:193
#: ../Doc/library/ssl.rst:194 ../Doc/library/ssl.rst:195
#: ../Doc/library/ssl.rst:196 ../Doc/library/ssl.rst:197
msgid "no"
msgstr "non"
#: ../Doc/library/ssl.rst:193
msgid "*SSLv3*"
msgstr "*SSLv3*"
#: ../Doc/library/ssl.rst:194
msgid "*TLS* (*SSLv23*)"
msgstr ""
#: ../Doc/library/ssl.rst:195
msgid "*TLSv1*"
msgstr "*TLSv1*"
#: ../Doc/library/ssl.rst:196
msgid "*TLSv1.1*"
msgstr "*TLSv1.1*"
#: ../Doc/library/ssl.rst:197
msgid "*TLSv1.2*"
msgstr "*TLSv1.2*"
#: ../Doc/library/ssl.rst:202
msgid ""
"Which connections succeed will vary depending on the version of OpenSSL. "
"For example, before OpenSSL 1.0.0, an SSLv23 client would always attempt "
"SSLv2 connections."
msgstr ""
#: ../Doc/library/ssl.rst:206
msgid ""
"The *ciphers* parameter sets the available ciphers for this SSL object. It "
"should be a string in the `OpenSSL cipher list format <https://www.openssl."
"org/docs/apps/ciphers.html#CIPHER-LIST-FORMAT>`_."
msgstr ""
#: ../Doc/library/ssl.rst:210
msgid ""
"The parameter ``do_handshake_on_connect`` specifies whether to do the SSL "
"handshake automatically after doing a :meth:`socket.connect`, or whether the "
"application program will call it explicitly, by invoking the :meth:"
"`SSLSocket.do_handshake` method. Calling :meth:`SSLSocket.do_handshake` "
"explicitly gives the program control over the blocking behavior of the "
"socket I/O involved in the handshake."
msgstr ""
#: ../Doc/library/ssl.rst:217
msgid ""
"The parameter ``suppress_ragged_eofs`` specifies how the :meth:`SSLSocket."
"recv` method should signal unexpected EOF from the other end of the "
"connection. If specified as :const:`True` (the default), it returns a "
"normal EOF (an empty bytes object) in response to unexpected EOF errors "
"raised from the underlying socket; if :const:`False`, it will raise the "
"exceptions back to the caller."
msgstr ""
#: ../Doc/library/ssl.rst:224
msgid "New optional argument *ciphers*."
msgstr ""
#: ../Doc/library/ssl.rst:229
msgid "Context creation"
msgstr "Création de contexte"
#: ../Doc/library/ssl.rst:231
msgid ""
"A convenience function helps create :class:`SSLContext` objects for common "
"purposes."
msgstr ""
"Une fonction utilitaire permettant de créer facilement des objets :class:"
"`SSLContext` pour des usages classiques."
#: ../Doc/library/ssl.rst:236
msgid ""
"Return a new :class:`SSLContext` object with default settings for the given "
"*purpose*. The settings are chosen by the :mod:`ssl` module, and usually "
"represent a higher security level than when calling the :class:`SSLContext` "
"constructor directly."
msgstr ""
"Renvoie un nouvel objet :class:`SSLContext`. Le paramètre *purpose* permet "
"de choisir parmi un ensemble de paramètres par défaut en fonction de l'usage "
"souhaité. Les paramètres sont choisis par le module :mod:`ssl` et "
"représentent généralement un niveau de sécurité supérieur à celui utilisé "
"lorsque vous appelez directement le constructeur :class:`SSLContext`."
#: ../Doc/library/ssl.rst:241
msgid ""
"*cafile*, *capath*, *cadata* represent optional CA certificates to trust for "
"certificate verification, as in :meth:`SSLContext.load_verify_locations`. "
"If all three are :const:`None`, this function can choose to trust the "
"system's default CA certificates instead."
msgstr ""
"*cafile*, *capath*, *cadata* représentent des certificats d'autorité de "
"certification facultatifs approuvés pour la vérification de certificats, "
"comme dans :meth:`SSLContext.load_verify_locations`. Si les trois sont à :"
"const:`None`, cette fonction peut choisir de faire confiance aux certificats "
"d'autorité de certification par défaut du système."
#: ../Doc/library/ssl.rst:247
msgid ""
"The settings are: :data:`PROTOCOL_TLS`, :data:`OP_NO_SSLv2`, and :data:"
"`OP_NO_SSLv3` with high encryption cipher suites without RC4 and without "
"unauthenticated cipher suites. Passing :data:`~Purpose.SERVER_AUTH` as "
"*purpose* sets :data:`~SSLContext.verify_mode` to :data:`CERT_REQUIRED` and "
"either loads CA certificates (when at least one of *cafile*, *capath* or "
"*cadata* is given) or uses :meth:`SSLContext.load_default_certs` to load "
"default CA certificates."
msgstr ""
"Les paramètres sont : :data:`PROTOCOL_TLS`, :data:`OP_NO_SSLv2` et :data:"
"`OP_NO_SSLv3` avec des algorithmes de chiffrement de grande robustesse, "
"n'utilisant pas RC4 et n'utilisant pas les suites cryptographiques sans "
"authentification. Passer :data:`~Purpose.SERVER_AUTH` en tant que *purpose* "
"définit :data:`~SSLContext.verify_mode` sur :data:`CERT_REQUIRED` et charge "
"les certificats de l'autorité de certification (lorsqu'au moins un des "
"paramètres *cafile*, *capath* ou *cadata* est renseigné) ou utilise :meth:"
"`SSLContext.load_default_certs` pour charger les certificats des autorités "
"de certification par défaut."
#: ../Doc/library/ssl.rst:256
msgid ""
"The protocol, options, cipher and other settings may change to more "
"restrictive values anytime without prior deprecation. The values represent "
"a fair balance between compatibility and security."
msgstr ""
"Le protocole, les options, l'algorithme de chiffrement et d'autres "
"paramètres peuvent changer pour des valeurs plus restrictives à tout moment "
"sans avertissement préalable. Les valeurs représentent un juste équilibre "
"entre compatibilité et sécurité."
#: ../Doc/library/ssl.rst:260
msgid ""
"If your application needs specific settings, you should create a :class:"
"`SSLContext` and apply the settings yourself."
msgstr ""
"Si votre application nécessite des paramètres spécifiques, vous devez créer "
"une classe :class:`SSLContext` et appliquer les paramètres vous-même."
#: ../Doc/library/ssl.rst:264
msgid ""
"If you find that when certain older clients or servers attempt to connect "
"with a :class:`SSLContext` created by this function that they get an error "
"stating \"Protocol or cipher suite mismatch\", it may be that they only "
"support SSL3.0 which this function excludes using the :data:`OP_NO_SSLv3`. "
"SSL3.0 is widely considered to be `completely broken <https://en.wikipedia."
"org/wiki/POODLE>`_. If you still wish to continue to use this function but "
"still allow SSL 3.0 connections you can re-enable them using::"
msgstr ""
"Si vous constatez que, lorsque certains clients ou serveurs plus anciens "
"tentent de se connecter avec une classe :class:`SSLContext` créée par cette "
"fonction, une erreur indiquant « *Protocol or cipher suite "
"mismatch* » (« Non concordance de protocole ou d'algorithme de "
"chiffrement ») est détectée, il se peut qu'ils ne prennent en charge que SSL "
"3.0 que cette fonction exclut en utilisant :data:`OP_NO_SSLv3`. SSL3.0 est "
"notoirement considéré comme `totalement déficient <https://fr.wikipedia.org/"
"wiki/POODLE>`_. Si vous souhaitez toujours continuer à utiliser cette "
"fonction tout en autorisant les connexions SSL 3.0, vous pouvez les "
"réactiver à l'aide de ::"
#: ../Doc/library/ssl.rst:280
msgid "RC4 was dropped from the default cipher string."
msgstr ""
"RC4 a été supprimé de la liste des algorithmes de chiffrement par défaut."
#: ../Doc/library/ssl.rst:284
msgid "ChaCha20/Poly1305 was added to the default cipher string."
msgstr ""
"*ChaCha20*/*Poly1305* a été ajouté à la liste des algorithmes de chiffrement "
"par défaut."
#: ../Doc/library/ssl.rst:286
msgid "3DES was dropped from the default cipher string."
msgstr ""
"*3DES* a été supprimé de la liste des algorithmes de chiffrement par défaut."
#: ../Doc/library/ssl.rst:290
msgid "Random generation"
msgstr ""
#: ../Doc/library/ssl.rst:294
msgid ""
"Return *num* cryptographically strong pseudo-random bytes. Raises an :class:"
"`SSLError` if the PRNG has not been seeded with enough data or if the "
"operation is not supported by the current RAND method. :func:`RAND_status` "
"can be used to check the status of the PRNG and :func:`RAND_add` can be used "
"to seed the PRNG."
msgstr ""
#: ../Doc/library/ssl.rst:300 ../Doc/library/ssl.rst:321
msgid "For almost all applications :func:`os.urandom` is preferable."
msgstr ""
#: ../Doc/library/ssl.rst:302
msgid ""
"Read the Wikipedia article, `Cryptographically secure pseudorandom number "
"generator (CSPRNG) <https://en.wikipedia.org/wiki/"
"Cryptographically_secure_pseudorandom_number_generator>`_, to get the "
"requirements of a cryptographically generator."
msgstr ""
#: ../Doc/library/ssl.rst:311
msgid ""
"Return (bytes, is_cryptographic): bytes are *num* pseudo-random bytes, "
"is_cryptographic is ``True`` if the bytes generated are cryptographically "
"strong. Raises an :class:`SSLError` if the operation is not supported by the "
"current RAND method."
msgstr ""
#: ../Doc/library/ssl.rst:316
msgid ""
"Generated pseudo-random byte sequences will be unique if they are of "
"sufficient length, but are not necessarily unpredictable. They can be used "
"for non-cryptographic purposes and for certain purposes in cryptographic "
"protocols, but usually not for key generation etc."
msgstr ""
#: ../Doc/library/ssl.rst:327
msgid ""
"OpenSSL has deprecated :func:`ssl.RAND_pseudo_bytes`, use :func:`ssl."
"RAND_bytes` instead."
msgstr ""
#: ../Doc/library/ssl.rst:332
msgid ""
"Return ``True`` if the SSL pseudo-random number generator has been seeded "
"with 'enough' randomness, and ``False`` otherwise. You can use :func:`ssl."
"RAND_egd` and :func:`ssl.RAND_add` to increase the randomness of the pseudo-"
"random number generator."
msgstr ""
#: ../Doc/library/ssl.rst:339
msgid ""
"If you are running an entropy-gathering daemon (EGD) somewhere, and *path* "
"is the pathname of a socket connection open to it, this will read 256 bytes "
"of randomness from the socket, and add it to the SSL pseudo-random number "
"generator to increase the security of generated secret keys. This is "
"typically only necessary on systems without better sources of randomness."
msgstr ""
#: ../Doc/library/ssl.rst:345
msgid ""
"See http://egd.sourceforge.net/ or http://prngd.sourceforge.net/ for sources "
"of entropy-gathering daemons."
msgstr ""
#: ../Doc/library/ssl.rst:348
msgid "Availability: not available with LibreSSL and OpenSSL > 1.1.0"
msgstr ""
#: ../Doc/library/ssl.rst:352
msgid ""
"Mix the given *bytes* into the SSL pseudo-random number generator. The "
"parameter *entropy* (a float) is a lower bound on the entropy contained in "
"string (so you can always use :const:`0.0`). See :rfc:`1750` for more "
"information on sources of entropy."
msgstr ""
#: ../Doc/library/ssl.rst:357
msgid "Writable :term:`bytes-like object` is now accepted."
msgstr "N'importe quel :term:`bytes-like object` est maintenant accepté."
#: ../Doc/library/ssl.rst:361
msgid "Certificate handling"
msgstr ""
#: ../Doc/library/ssl.rst:365
msgid ""
"Verify that *cert* (in decoded format as returned by :meth:`SSLSocket."
"getpeercert`) matches the given *hostname*. The rules applied are those for "
"checking the identity of HTTPS servers as outlined in :rfc:`2818` and :rfc:"
"`6125`. In addition to HTTPS, this function should be suitable for checking "
"the identity of servers in various SSL-based protocols such as FTPS, IMAPS, "
"POPS and others."
msgstr ""
#: ../Doc/library/ssl.rst:372
msgid ""
":exc:`CertificateError` is raised on failure. On success, the function "
"returns nothing::"
msgstr ""
#: ../Doc/library/ssl.rst:385
msgid ""
"The function now follows :rfc:`6125`, section 6.4.3 and does neither match "
"multiple wildcards (e.g. ``*.*.com`` or ``*a*.example.org``) nor a wildcard "
"inside an internationalized domain names (IDN) fragment. IDN A-labels such "
"as ``www*.xn--pthon-kva.org`` are still supported, but ``x*.python.org`` no "
"longer matches ``xn--tda.python.org``."
msgstr ""
#: ../Doc/library/ssl.rst:392
msgid ""
"Matching of IP addresses, when present in the subjectAltName field of the "
"certificate, is now supported."
msgstr ""
#: ../Doc/library/ssl.rst:398
msgid ""
"Return the time in seconds since the Epoch, given the ``cert_time`` string "
"representing the \"notBefore\" or \"notAfter\" date from a certificate in ``"
"\"%b %d %H:%M:%S %Y %Z\"`` strptime format (C locale)."
msgstr ""
#: ../Doc/library/ssl.rst:403
msgid "Here's an example:"
msgstr ""
#: ../Doc/library/ssl.rst:415
msgid "\"notBefore\" or \"notAfter\" dates must use GMT (:rfc:`5280`)."
msgstr ""
#: ../Doc/library/ssl.rst:417
msgid ""
"Interpret the input time as a time in UTC as specified by 'GMT' timezone in "
"the input string. Local timezone was used previously. Return an integer (no "
"fractions of a second in the input format)"
msgstr ""
#: ../Doc/library/ssl.rst:425
msgid ""
"Given the address ``addr`` of an SSL-protected server, as a (*hostname*, "
"*port-number*) pair, fetches the server's certificate, and returns it as a "
"PEM-encoded string. If ``ssl_version`` is specified, uses that version of "
"the SSL protocol to attempt to connect to the server. If ``ca_certs`` is "
"specified, it should be a file containing a list of root certificates, the "
"same format as used for the same parameter in :func:`wrap_socket`. The call "
"will attempt to validate the server certificate against that set of root "
"certificates, and will fail if the validation attempt fails."
msgstr ""
#: ../Doc/library/ssl.rst:434
msgid "This function is now IPv6-compatible."
msgstr ""
#: ../Doc/library/ssl.rst:437
msgid ""
"The default *ssl_version* is changed from :data:`PROTOCOL_SSLv3` to :data:"
"`PROTOCOL_TLS` for maximum compatibility with modern servers."
msgstr ""
#: ../Doc/library/ssl.rst:443
msgid ""
"Given a certificate as a DER-encoded blob of bytes, returns a PEM-encoded "
"string version of the same certificate."
msgstr ""
#: ../Doc/library/ssl.rst:448
msgid ""
"Given a certificate as an ASCII PEM string, returns a DER-encoded sequence "
"of bytes for that same certificate."
msgstr ""
#: ../Doc/library/ssl.rst:453
msgid ""
"Returns a named tuple with paths to OpenSSL's default cafile and capath. The "
"paths are the same as used by :meth:`SSLContext.set_default_verify_paths`. "
"The return value is a :term:`named tuple` ``DefaultVerifyPaths``:"
msgstr ""
#: ../Doc/library/ssl.rst:458
msgid ""
":attr:`cafile` - resolved path to cafile or ``None`` if the file doesn't "
"exist,"
msgstr ""
#: ../Doc/library/ssl.rst:459
msgid ""
":attr:`capath` - resolved path to capath or ``None`` if the directory "
"doesn't exist,"
msgstr ""
#: ../Doc/library/ssl.rst:460
msgid ""
":attr:`openssl_cafile_env` - OpenSSL's environment key that points to a "
"cafile,"
msgstr ""
#: ../Doc/library/ssl.rst:461
msgid ":attr:`openssl_cafile` - hard coded path to a cafile,"
msgstr ""
#: ../Doc/library/ssl.rst:462
msgid ""
":attr:`openssl_capath_env` - OpenSSL's environment key that points to a "
"capath,"
msgstr ""
#: ../Doc/library/ssl.rst:463
msgid ":attr:`openssl_capath` - hard coded path to a capath directory"
msgstr ""
#: ../Doc/library/ssl.rst:465
msgid ""
"Availability: LibreSSL ignores the environment vars :attr:"
"`openssl_cafile_env` and :attr:`openssl_capath_env`"
msgstr ""
#: ../Doc/library/ssl.rst:472
msgid ""
"Retrieve certificates from Windows' system cert store. *store_name* may be "
"one of ``CA``, ``ROOT`` or ``MY``. Windows may provide additional cert "
"stores, too."
msgstr ""
#: ../Doc/library/ssl.rst:476
msgid ""
"The function returns a list of (cert_bytes, encoding_type, trust) tuples. "
"The encoding_type specifies the encoding of cert_bytes. It is either :const:"
"`x509_asn` for X.509 ASN.1 data or :const:`pkcs_7_asn` for PKCS#7 ASN.1 "
"data. Trust specifies the purpose of the certificate as a set of OIDS or "
"exactly ``True`` if the certificate is trustworthy for all purposes."
msgstr ""
#: ../Doc/library/ssl.rst:483 ../Doc/library/ssl.rst:1451
msgid "Example::"
msgstr "Exemple ::"
#: ../Doc/library/ssl.rst:489 ../Doc/library/ssl.rst:504
msgid "Availability: Windows."
msgstr "Disponibilité : Windows."
#: ../Doc/library/ssl.rst:495
msgid ""
"Retrieve CRLs from Windows' system cert store. *store_name* may be one of "
"``CA``, ``ROOT`` or ``MY``. Windows may provide additional cert stores, too."
msgstr ""
#: ../Doc/library/ssl.rst:499
msgid ""
"The function returns a list of (cert_bytes, encoding_type, trust) tuples. "
"The encoding_type specifies the encoding of cert_bytes. It is either :const:"
"`x509_asn` for X.509 ASN.1 data or :const:`pkcs_7_asn` for PKCS#7 ASN.1 data."
msgstr ""
#: ../Doc/library/ssl.rst:510
msgid "Constants"
msgstr "Constantes"
#: ../Doc/library/ssl.rst:514
msgid ""
"Possible value for :attr:`SSLContext.verify_mode`, or the ``cert_reqs`` "
"parameter to :func:`wrap_socket`. In this mode (the default), no "
"certificates will be required from the other side of the socket connection. "
"If a certificate is received from the other end, no attempt to validate it "
"is made."
msgstr ""
#: ../Doc/library/ssl.rst:520 ../Doc/library/ssl.rst:1753
msgid "See the discussion of :ref:`ssl-security` below."
msgstr ""
#: ../Doc/library/ssl.rst:524
msgid ""
"Possible value for :attr:`SSLContext.verify_mode`, or the ``cert_reqs`` "
"parameter to :func:`wrap_socket`. In this mode no certificates will be "
"required from the other side of the socket connection; but if they are "
"provided, validation will be attempted and an :class:`SSLError` will be "
"raised on failure."
msgstr ""
#: ../Doc/library/ssl.rst:530 ../Doc/library/ssl.rst:541
msgid ""
"Use of this setting requires a valid set of CA certificates to be passed, "
"either to :meth:`SSLContext.load_verify_locations` or as a value of the "
"``ca_certs`` parameter to :func:`wrap_socket`."
msgstr ""
#: ../Doc/library/ssl.rst:536
msgid ""
"Possible value for :attr:`SSLContext.verify_mode`, or the ``cert_reqs`` "
"parameter to :func:`wrap_socket`. In this mode, certificates are required "
"from the other side of the socket connection; an :class:`SSLError` will be "
"raised if no certificate is provided, or if its validation fails."
msgstr ""
#: ../Doc/library/ssl.rst:547
msgid ""
"Possible value for :attr:`SSLContext.verify_flags`. In this mode, "
"certificate revocation lists (CRLs) are not checked. By default OpenSSL does "
"neither require nor verify CRLs."
msgstr ""
#: ../Doc/library/ssl.rst:555
msgid ""
"Possible value for :attr:`SSLContext.verify_flags`. In this mode, only the "
"peer cert is check but non of the intermediate CA certificates. The mode "
"requires a valid CRL that is signed by the peer cert's issuer (its direct "
"ancestor CA). If no proper has been loaded :attr:`SSLContext."
"load_verify_locations`, validation will fail."
msgstr ""
#: ../Doc/library/ssl.rst:565
msgid ""
"Possible value for :attr:`SSLContext.verify_flags`. In this mode, CRLs of "
"all certificates in the peer cert chain are checked."
msgstr ""
#: ../Doc/library/ssl.rst:572
msgid ""
"Possible value for :attr:`SSLContext.verify_flags` to disable workarounds "
"for broken X.509 certificates."
msgstr ""
#: ../Doc/library/ssl.rst:579
msgid ""
"Possible value for :attr:`SSLContext.verify_flags`. It instructs OpenSSL to "
"prefer trusted certificates when building the trust chain to validate a "
"certificate. This flag is enabled by default."
msgstr ""
#: ../Doc/library/ssl.rst:587
msgid ""
"Selects the highest protocol version that both the client and server "
"support. Despite the name, this option can select \"TLS\" protocols as well "
"as \"SSL\"."
msgstr ""
#: ../Doc/library/ssl.rst:594
msgid "Alias for data:`PROTOCOL_TLS`."
msgstr ""
#: ../Doc/library/ssl.rst:598
msgid "Use data:`PROTOCOL_TLS` instead."
msgstr ""
#: ../Doc/library/ssl.rst:602
msgid "Selects SSL version 2 as the channel encryption protocol."
msgstr ""
#: ../Doc/library/ssl.rst:604
msgid ""
"This protocol is not available if OpenSSL is compiled with the "
"``OPENSSL_NO_SSL2`` flag."
msgstr ""
#: ../Doc/library/ssl.rst:609
msgid "SSL version 2 is insecure. Its use is highly discouraged."
msgstr ""
#: ../Doc/library/ssl.rst:613
msgid "OpenSSL has removed support for SSLv2."
msgstr ""
#: ../Doc/library/ssl.rst:617
msgid "Selects SSL version 3 as the channel encryption protocol."
msgstr ""
#: ../Doc/library/ssl.rst:619
msgid ""
"This protocol is not be available if OpenSSL is compiled with the "
"``OPENSSL_NO_SSLv3`` flag."
msgstr ""
#: ../Doc/library/ssl.rst:624
msgid "SSL version 3 is insecure. Its use is highly discouraged."
msgstr ""
#: ../Doc/library/ssl.rst:628 ../Doc/library/ssl.rst:637
#: ../Doc/library/ssl.rst:649 ../Doc/library/ssl.rst:662
msgid ""
"OpenSSL has deprecated all version specific protocols. Use the default "
"protocol data:`PROTOCOL_TLS` with flags like data:`OP_NO_SSLv3` instead."
msgstr ""
#: ../Doc/library/ssl.rst:633
msgid "Selects TLS version 1.0 as the channel encryption protocol."
msgstr ""
#: ../Doc/library/ssl.rst:642
msgid ""
"Selects TLS version 1.1 as the channel encryption protocol. Available only "
"with openssl version 1.0.1+."
msgstr ""
#: ../Doc/library/ssl.rst:654
msgid ""
"Selects TLS version 1.2 as the channel encryption protocol. This is the most "
"modern version, and probably the best choice for maximum protection, if both "
"sides can speak it. Available only with openssl version 1.0.1+."
msgstr ""
#: ../Doc/library/ssl.rst:667
msgid ""
"Enables workarounds for various bugs present in other SSL implementations. "
"This option is set by default. It does not necessarily set the same flags "
"as OpenSSL's ``SSL_OP_ALL`` constant."
msgstr ""
#: ../Doc/library/ssl.rst:675
msgid ""
"Prevents an SSLv2 connection. This option is only applicable in conjunction "
"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing SSLv2 as "
"the protocol version."
msgstr ""
#: ../Doc/library/ssl.rst:683
msgid "SSLv2 is deprecated"
msgstr ""
#: ../Doc/library/ssl.rst:688
msgid ""
"Prevents an SSLv3 connection. This option is only applicable in conjunction "
"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing SSLv3 as "
"the protocol version."
msgstr ""
#: ../Doc/library/ssl.rst:696
msgid "SSLv3 is deprecated"
msgstr ""
#: ../Doc/library/ssl.rst:700
msgid ""
"Prevents a TLSv1 connection. This option is only applicable in conjunction "
"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing TLSv1 as "
"the protocol version."
msgstr ""
#: ../Doc/library/ssl.rst:708
msgid ""
"Prevents a TLSv1.1 connection. This option is only applicable in conjunction "
"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing TLSv1.1 as "
"the protocol version. Available only with openssl version 1.0.1+."
msgstr ""
#: ../Doc/library/ssl.rst:716
msgid ""
"Prevents a TLSv1.2 connection. This option is only applicable in conjunction "
"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing TLSv1.2 as "
"the protocol version. Available only with openssl version 1.0.1+."
msgstr ""
#: ../Doc/library/ssl.rst:724
msgid ""
"Use the server's cipher ordering preference, rather than the client's. This "
"option has no effect on client sockets and SSLv2 server sockets."
msgstr ""
#: ../Doc/library/ssl.rst:731
msgid ""
"Prevents re-use of the same DH key for distinct SSL sessions. This improves "
"forward secrecy but requires more computational resources. This option only "
"applies to server sockets."
msgstr ""
#: ../Doc/library/ssl.rst:739
msgid ""
"Prevents re-use of the same ECDH key for distinct SSL sessions. This "
"improves forward secrecy but requires more computational resources. This "
"option only applies to server sockets."
msgstr ""
#: ../Doc/library/ssl.rst:747
msgid ""
"Disable compression on the SSL channel. This is useful if the application "
"protocol supports its own compression scheme."
msgstr ""
#: ../Doc/library/ssl.rst:750
msgid "This option is only available with OpenSSL 1.0.0 and later."
msgstr ""
#: ../Doc/library/ssl.rst:756
msgid ""
"Whether the OpenSSL library has built-in support for the *Application-Layer "
"Protocol Negotiation* TLS extension as described in :rfc:`7301`."
msgstr ""
#: ../Doc/library/ssl.rst:763
msgid ""
"Whether the OpenSSL library has built-in support for Elliptic Curve-based "
"Diffie-Hellman key exchange. This should be true unless the feature was "
"explicitly disabled by the distributor."
msgstr ""
#: ../Doc/library/ssl.rst:771
msgid ""
"Whether the OpenSSL library has built-in support for the *Server Name "
"Indication* extension (as defined in :rfc:`4366`)."
msgstr ""
#: ../Doc/library/ssl.rst:778
msgid ""
"Whether the OpenSSL library has built-in support for *Next Protocol "
"Negotiation* as described in the `NPN draft specification <https://tools."
"ietf.org/html/draft-agl-tls-nextprotoneg>`_. When true, you can use the :"
"meth:`SSLContext.set_npn_protocols` method to advertise which protocols you "
"want to support."
msgstr ""
#: ../Doc/library/ssl.rst:788
msgid ""
"List of supported TLS channel binding types. Strings in this list can be "
"used as arguments to :meth:`SSLSocket.get_channel_binding`."
msgstr ""
#: ../Doc/library/ssl.rst:795
msgid "The version string of the OpenSSL library loaded by the interpreter::"
msgstr ""
#: ../Doc/library/ssl.rst:804
msgid ""
"A tuple of five integers representing version information about the OpenSSL "
"library::"
msgstr ""
#: ../Doc/library/ssl.rst:814
msgid "The raw version number of the OpenSSL library, as a single integer::"
msgstr ""
#: ../Doc/library/ssl.rst:827
msgid ""
"Alert Descriptions from :rfc:`5246` and others. The `IANA TLS Alert Registry "
"<https://www.iana.org/assignments/tls-parameters/tls-parameters.xml#tls-"
"parameters-6>`_ contains this list and references to the RFCs where their "
"meaning is defined."
msgstr ""
#: ../Doc/library/ssl.rst:831
msgid ""
"Used as the return value of the callback function in :meth:`SSLContext."
"set_servername_callback`."
msgstr ""
#: ../Doc/library/ssl.rst:838
msgid ""
"Option for :func:`create_default_context` and :meth:`SSLContext."
"load_default_certs`. This value indicates that the context may be used to "
"authenticate Web servers (therefore, it will be used to create client-side "
"sockets)."
msgstr ""
#: ../Doc/library/ssl.rst:847
msgid ""
"Option for :func:`create_default_context` and :meth:`SSLContext."
"load_default_certs`. This value indicates that the context may be used to "
"authenticate Web clients (therefore, it will be used to create server-side "
"sockets)."
msgstr ""
#: ../Doc/library/ssl.rst:856
msgid "SSL Sockets"
msgstr ""
#: ../Doc/library/ssl.rst:860
msgid "SSL sockets provide the following methods of :ref:`socket-objects`:"
msgstr ""
#: ../Doc/library/ssl.rst:862
msgid ":meth:`~socket.socket.accept()`"
msgstr ""
#: ../Doc/library/ssl.rst:863
msgid ":meth:`~socket.socket.bind()`"
msgstr ""
#: ../Doc/library/ssl.rst:864
msgid ":meth:`~socket.socket.close()`"
msgstr ""
#: ../Doc/library/ssl.rst:865
msgid ":meth:`~socket.socket.connect()`"
msgstr ""
#: ../Doc/library/ssl.rst:866
msgid ":meth:`~socket.socket.detach()`"
msgstr ""
#: ../Doc/library/ssl.rst:867
msgid ":meth:`~socket.socket.fileno()`"
msgstr ""
#: ../Doc/library/ssl.rst:868
msgid ""
":meth:`~socket.socket.getpeername()`, :meth:`~socket.socket.getsockname()`"
msgstr ""
#: ../Doc/library/ssl.rst:869
msgid ""
":meth:`~socket.socket.getsockopt()`, :meth:`~socket.socket.setsockopt()`"
msgstr ""
#: ../Doc/library/ssl.rst:870
msgid ""
":meth:`~socket.socket.gettimeout()`, :meth:`~socket.socket.settimeout()`, :"
"meth:`~socket.socket.setblocking()`"
msgstr ""
#: ../Doc/library/ssl.rst:872
msgid ":meth:`~socket.socket.listen()`"
msgstr ""
#: ../Doc/library/ssl.rst:873
msgid ":meth:`~socket.socket.makefile()`"
msgstr ""
#: ../Doc/library/ssl.rst:874
msgid ""
":meth:`~socket.socket.recv()`, :meth:`~socket.socket.recv_into()` (but "
"passing a non-zero ``flags`` argument is not allowed)"
msgstr ""
#: ../Doc/library/ssl.rst:876
msgid ""
":meth:`~socket.socket.send()`, :meth:`~socket.socket.sendall()` (with the "
"same limitation)"
msgstr ""
#: ../Doc/library/ssl.rst:878
msgid ""
":meth:`~socket.socket.sendfile()` (but :mod:`os.sendfile` will be used for "
"plain-text sockets only, else :meth:`~socket.socket.send()` will be used)"
msgstr ""
#: ../Doc/library/ssl.rst:880
msgid ":meth:`~socket.socket.shutdown()`"
msgstr ""
#: ../Doc/library/ssl.rst:882
msgid ""
"However, since the SSL (and TLS) protocol has its own framing atop of TCP, "
"the SSL sockets abstraction can, in certain respects, diverge from the "
"specification of normal, OS-level sockets. See especially the :ref:`notes "
"on non-blocking sockets <ssl-nonblocking>`."
msgstr ""
#: ../Doc/library/ssl.rst:887
msgid ""
"Usually, :class:`SSLSocket` are not created directly, but using the :func:"
"`wrap_socket` function or the :meth:`SSLContext.wrap_socket` method."
msgstr ""
#: ../Doc/library/ssl.rst:890
msgid "The :meth:`sendfile` method was added."
msgstr ""
#: ../Doc/library/ssl.rst:893
msgid ""
"The :meth:`shutdown` does not reset the socket timeout each time bytes are "
"received or sent. The socket timeout is now to maximum total duration of the "
"shutdown."
msgstr ""
#: ../Doc/library/ssl.rst:899
msgid "SSL sockets also have the following additional methods and attributes:"
msgstr ""
#: ../Doc/library/ssl.rst:903
msgid ""
"Read up to *len* bytes of data from the SSL socket and return the result as "
"a ``bytes`` instance. If *buffer* is specified, then read into the buffer "
"instead, and return the number of bytes read."
msgstr ""
#: ../Doc/library/ssl.rst:907
msgid ""
"Raise :exc:`SSLWantReadError` or :exc:`SSLWantWriteError` if the socket is :"
"ref:`non-blocking <ssl-nonblocking>` and the read would block."
msgstr ""
#: ../Doc/library/ssl.rst:910
msgid ""
"As at any time a re-negotiation is possible, a call to :meth:`read` can also "
"cause write operations."
msgstr ""
#: ../Doc/library/ssl.rst:913
msgid ""
"The socket timeout is no more reset each time bytes are received or sent. "
"The socket timeout is now to maximum total duration to read up to *len* "
"bytes."
msgstr ""
#: ../Doc/library/ssl.rst:920
msgid ""
"Write *buf* to the SSL socket and return the number of bytes written. The "
"*buf* argument must be an object supporting the buffer interface."
msgstr ""
#: ../Doc/library/ssl.rst:923
msgid ""
"Raise :exc:`SSLWantReadError` or :exc:`SSLWantWriteError` if the socket is :"
"ref:`non-blocking <ssl-nonblocking>` and the write would block."
msgstr ""
#: ../Doc/library/ssl.rst:926
msgid ""
"As at any time a re-negotiation is possible, a call to :meth:`write` can "
"also cause read operations."
msgstr ""
#: ../Doc/library/ssl.rst:929
msgid ""
"The socket timeout is no more reset each time bytes are received or sent. "
"The socket timeout is now to maximum total duration to write *buf*."
msgstr ""
#: ../Doc/library/ssl.rst:935
msgid ""
"The :meth:`~SSLSocket.read` and :meth:`~SSLSocket.write` methods are the low-"
"level methods that read and write unencrypted, application-level data and "
"decrypt/encrypt it to encrypted, wire-level data. These methods require an "
"active SSL connection, i.e. the handshake was completed and :meth:`SSLSocket."
"unwrap` was not called."
msgstr ""
#: ../Doc/library/ssl.rst:941
msgid ""
"Normally you should use the socket API methods like :meth:`~socket.socket."
"recv` and :meth:`~socket.socket.send` instead of these methods."
msgstr ""
#: ../Doc/library/ssl.rst:947
msgid "Perform the SSL setup handshake."
msgstr ""
#: ../Doc/library/ssl.rst:949
msgid ""
"The handshake method also performs :func:`match_hostname` when the :attr:"
"`~SSLContext.check_hostname` attribute of the socket's :attr:`~SSLSocket."
"context` is true."
msgstr ""
#: ../Doc/library/ssl.rst:954
msgid ""
"The socket timeout is no more reset each time bytes are received or sent. "
"The socket timeout is now to maximum total duration of the handshake."
msgstr ""
#: ../Doc/library/ssl.rst:960
msgid ""
"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, raise :exc:"
"`ValueError`."
msgstr ""
#: ../Doc/library/ssl.rst:964
msgid ""
"If the ``binary_form`` parameter is :const:`False`, and a certificate was "
"received from the peer, this method returns a :class:`dict` instance. If "
"the certificate was not validated, the dict is empty. If the certificate "
"was validated, it returns a dict with several keys, amongst them ``subject`` "
"(the principal for which the certificate was issued) and ``issuer`` (the "
"principal issuing the certificate). If a certificate contains an instance "
"of the *Subject Alternative Name* extension (see :rfc:`3280`), there will "
"also be a ``subjectAltName`` key in the dictionary."
msgstr ""
#: ../Doc/library/ssl.rst:973
msgid ""
"The ``subject`` and ``issuer`` fields are tuples containing the sequence of "
"relative distinguished names (RDNs) given in the certificate's data "
"structure for the respective fields, and each RDN is a sequence of name-"
"value pairs. Here is a real-world example::"
msgstr ""
#: ../Doc/library/ssl.rst:999
msgid ""
"To validate a certificate for a particular service, you can use the :func:"
"`match_hostname` function."
msgstr ""
#: ../Doc/library/ssl.rst:1002
msgid ""
"If the ``binary_form`` parameter is :const:`True`, and a certificate was "
"provided, this method returns the DER-encoded form of the entire certificate "
"as a sequence of bytes, or :const:`None` if the peer did not provide a "
"certificate. Whether the peer provides a certificate depends on the SSL "
"socket's role:"
msgstr ""
#: ../Doc/library/ssl.rst:1008
msgid ""
"for a client SSL socket, the server will always provide a certificate, "
"regardless of whether validation was required;"
msgstr ""
#: ../Doc/library/ssl.rst:1011
msgid ""
"for a server SSL socket, the client will only provide a certificate when "
"requested by the server; therefore :meth:`getpeercert` will return :const:"
"`None` if you used :const:`CERT_NONE` (rather than :const:`CERT_OPTIONAL` "
"or :const:`CERT_REQUIRED`)."
msgstr ""
#: ../Doc/library/ssl.rst:1016
msgid ""
"The returned dictionary includes additional items such as ``issuer`` and "
"``notBefore``."
msgstr ""
#: ../Doc/library/ssl.rst:1020
msgid ""
":exc:`ValueError` is raised when the handshake isn't done. The returned "
"dictionary includes additional X509v3 extension items such as "
"``crlDistributionPoints``, ``caIssuers`` and ``OCSP`` URIs."
msgstr ""
#: ../Doc/library/ssl.rst:1027
msgid ""
"Returns a three-value tuple containing the name of the cipher being used, "
"the version of the SSL protocol that defines its use, and the number of "
"secret bits being used. If no connection has been established, returns "
"``None``."
msgstr ""
#: ../Doc/library/ssl.rst:1033
msgid ""
"Return the list of ciphers shared by the client during the handshake. Each "
"entry of the returned list is a three-value tuple containing the name of the "
"cipher, the version of the SSL protocol that defines its use, and the number "
"of secret bits the cipher uses. :meth:`~SSLSocket.shared_ciphers` returns "
"``None`` if no connection has been established or the socket is a client "
"socket."
msgstr ""
#: ../Doc/library/ssl.rst:1044
msgid ""
"Return the compression algorithm being used as a string, or ``None`` if the "
"connection isn't compressed."
msgstr ""
#: ../Doc/library/ssl.rst:1047
msgid ""
"If the higher-level protocol supports its own compression mechanism, you can "
"use :data:`OP_NO_COMPRESSION` to disable SSL-level compression."
msgstr ""
#: ../Doc/library/ssl.rst:1054
msgid ""
"Get channel binding data for current connection, as a bytes object. Returns "
"``None`` if not connected or the handshake has not been completed."
msgstr ""
#: ../Doc/library/ssl.rst:1057
msgid ""
"The *cb_type* parameter allow selection of the desired channel binding type. "
"Valid channel binding types are listed in the :data:`CHANNEL_BINDING_TYPES` "
"list. Currently only the 'tls-unique' channel binding, defined by :rfc:"
"`5929`, is supported. :exc:`ValueError` will be raised if an unsupported "
"channel binding type is requested."
msgstr ""
#: ../Doc/library/ssl.rst:1067
msgid ""
"Return the protocol that was selected during the TLS handshake. If :meth:"
"`SSLContext.set_alpn_protocols` was not called, if the other party does not "
"support ALPN, if this socket does not support any of the client's proposed "
"protocols, or if the handshake has not happened yet, ``None`` is returned."
msgstr ""
#: ../Doc/library/ssl.rst:1077
msgid ""
"Return the higher-level protocol that was selected during the TLS/SSL "
"handshake. If :meth:`SSLContext.set_npn_protocols` was not called, or if the "
"other party does not support NPN, or if the handshake has not yet happened, "
"this will return ``None``."
msgstr ""
#: ../Doc/library/ssl.rst:1086
msgid ""
"Performs the SSL shutdown handshake, which removes the TLS layer from the "
"underlying socket, and returns the underlying socket object. This can be "
"used to go from encrypted operation over a connection to unencrypted. The "
"returned socket should always be used for further communication with the "
"other side of the connection, rather than the original socket."
msgstr ""
#: ../Doc/library/ssl.rst:1094
msgid ""
"Return the actual SSL protocol version negotiated by the connection as a "
"string, or ``None`` is 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."
msgstr ""
#: ../Doc/library/ssl.rst:1104
msgid ""
"Returns the number of already decrypted bytes available for read, pending on "
"the connection."
msgstr ""
#: ../Doc/library/ssl.rst:1109
msgid ""
"The :class:`SSLContext` object this SSL socket is tied to. If the SSL "
"socket was created using the top-level :func:`wrap_socket` function (rather "
"than :meth:`SSLContext.wrap_socket`), this is a custom context object "
"created for this SSL socket."
msgstr ""
#: ../Doc/library/ssl.rst:1118
msgid ""
"A boolean which is ``True`` for server-side sockets and ``False`` for client-"
"side sockets."
msgstr ""
#: ../Doc/library/ssl.rst:1125
msgid ""
"Hostname of the server: :class:`str` type, or ``None`` for server-side "
"socket or if the hostname was not specified in the constructor."
msgstr ""
#: ../Doc/library/ssl.rst:1132
msgid "SSL Contexts"
msgstr ""
#: ../Doc/library/ssl.rst:1136
msgid ""
"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 order to "
"speed up repeated connections from the same clients."
msgstr ""
#: ../Doc/library/ssl.rst:1143
msgid ""
"Create a new SSL context. You may pass *protocol* which must be one of the "
"``PROTOCOL_*`` constants defined in this module. :data:`PROTOCOL_TLS` is "
"currently recommended for maximum interoperability and default value."
msgstr ""
#: ../Doc/library/ssl.rst:1149
msgid ""
":func:`create_default_context` lets the :mod:`ssl` module choose security "
"settings for a given purpose."
msgstr ""
#: ../Doc/library/ssl.rst:1154
msgid ":data:`PROTOCOL_TLS` is the default value."
msgstr ""
#: ../Doc/library/ssl.rst:1157
msgid ":class:`SSLContext` objects have the following methods and attributes:"
msgstr ""
#: ../Doc/library/ssl.rst:1161
msgid ""
"Get statistics about quantities of loaded X.509 certificates, count of X.509 "
"certificates flagged as CA certificates and certificate revocation lists as "
"dictionary."
msgstr ""
#: ../Doc/library/ssl.rst:1165
msgid "Example for a context with one CA cert and one other cert::"
msgstr ""
#: ../Doc/library/ssl.rst:1175
msgid ""
"Load a private key and the corresponding certificate. The *certfile* string "
"must be the path to a single file in PEM format containing the certificate "
"as well as any number of CA certificates needed to establish the "
"certificate's authenticity. The *keyfile* string, if present, must point to "
"a file containing the private key in. Otherwise the private key will be "
"taken from *certfile* as well. See the discussion of :ref:`ssl-"
"certificates` for more information on how the certificate is stored in the "
"*certfile*."
msgstr ""
#: ../Doc/library/ssl.rst:1184
msgid ""
"The *password* argument may be a function to call to get the password for "
"decrypting the private key. It will only be called if the private key is "
"encrypted 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 is "
"a 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 directly "
"as the *password* argument. It will be ignored if the private key is not "
"encrypted and no password is needed."
msgstr ""
#: ../Doc/library/ssl.rst:1193
msgid ""
"If the *password* argument is not specified and a password is required, "
"OpenSSL's built-in password prompting mechanism will be used to "
"interactively prompt the user for a password."
msgstr ""
#: ../Doc/library/ssl.rst:1197
msgid ""
"An :class:`SSLError` is raised if the private key doesn't match with the "
"certificate."
msgstr ""
#: ../Doc/library/ssl.rst:1200
msgid "New optional argument *password*."
msgstr ""
#: ../Doc/library/ssl.rst:1205
msgid ""
"Load a set of default \"certification authority\" (CA) certificates from "
"default locations. On Windows it loads CA certs from the ``CA`` and ``ROOT`` "
"system stores. On other systems it calls :meth:`SSLContext."
"set_default_verify_paths`. In the future the method may load CA certificates "
"from other locations, too."
msgstr ""
#: ../Doc/library/ssl.rst:1211
msgid ""
"The *purpose* flag specifies what kind of CA certificates are loaded. The "
"default settings :data:`Purpose.SERVER_AUTH` loads certificates, that are "
"flagged and trusted for TLS web server authentication (client side "
"sockets). :data:`Purpose.CLIENT_AUTH` loads CA certificates for client "
"certificate verification on the server side."
msgstr ""
#: ../Doc/library/ssl.rst:1221
msgid ""
"Load a set of \"certification authority\" (CA) certificates used to validate "
"other peers' certificates when :data:`verify_mode` is other than :data:"
"`CERT_NONE`. At least one of *cafile* or *capath* must be specified."
msgstr ""
#: ../Doc/library/ssl.rst:1225
msgid ""
"This method can also load certification revocation lists (CRLs) in PEM or "
"DER format. In order to make use of CRLs, :attr:`SSLContext.verify_flags` "
"must be configured properly."
msgstr ""
#: ../Doc/library/ssl.rst:1229
msgid ""
"The *cafile* string, if present, is the path to a file of concatenated CA "
"certificates in PEM format. See the discussion of :ref:`ssl-certificates` "
"for more information about how to arrange the certificates in this file."
msgstr ""
#: ../Doc/library/ssl.rst:1234
msgid ""
"The *capath* string, if present, is the path to a directory containing "
"several CA certificates in PEM format, following an `OpenSSL specific layout "
"<https://www.openssl.org/docs/ssl/SSL_CTX_load_verify_locations.html>`_."
msgstr ""
#: ../Doc/library/ssl.rst:1239
msgid ""
"The *cadata* object, if present, is either an ASCII string of one or more "
"PEM-encoded certificates or a :term:`bytes-like object` of DER-encoded "
"certificates. Like with *capath* extra lines around PEM-encoded certificates "
"are ignored but at least one certificate must be present."
msgstr ""
#: ../Doc/library/ssl.rst:1244
msgid "New optional argument *cadata*"
msgstr ""
#: ../Doc/library/ssl.rst:1249
msgid ""
"Get a list of loaded \"certification authority\" (CA) certificates. If the "
"``binary_form`` parameter is :const:`False` each list entry is a dict like "
"the output of :meth:`SSLSocket.getpeercert`. Otherwise the method returns a "
"list of DER-encoded certificates. The returned list does not contain "
"certificates from *capath* unless a certificate was requested and loaded by "
"a SSL connection."
msgstr ""
#: ../Doc/library/ssl.rst:1257
msgid ""
"Certificates in a capath directory aren't loaded unless they have been used "
"at least once."
msgstr ""
#: ../Doc/library/ssl.rst:1264
msgid ""
"Load a set of default \"certification authority\" (CA) certificates from a "
"filesystem path defined when building the OpenSSL library. Unfortunately, "
"there's no easy way to know whether this method succeeds: no error is "
"returned if no certificates are to be found. When the OpenSSL library is "
"provided as part of the operating system, though, it is likely to be "
"configured properly."
msgstr ""
#: ../Doc/library/ssl.rst:1273
msgid ""
"Set the available ciphers for sockets created with this context. It should "
"be a string in the `OpenSSL cipher list format <https://www.openssl.org/docs/"
"apps/ciphers.html#CIPHER-LIST-FORMAT>`_. If no cipher can be selected "
"(because compile-time options or other configuration forbids use of all the "
"specified ciphers), an :class:`SSLError` will be raised."
msgstr ""
#: ../Doc/library/ssl.rst:1281
msgid ""
"when connected, the :meth:`SSLSocket.cipher` method of SSL sockets will give "
"the currently selected cipher."
msgstr ""
#: ../Doc/library/ssl.rst:1286
msgid ""
"Specify which protocols the socket should advertise during the SSL/TLS "
"handshake. It should be a list of ASCII strings, like ``['http/1.1', "
"'spdy/2']``, ordered by preference. The selection of a protocol will happen "
"during the handshake, and will play out according to :rfc:`7301`. After a "
"successful handshake, the :meth:`SSLSocket.selected_alpn_protocol` method "
"will return the agreed-upon protocol."
msgstr ""
#: ../Doc/library/ssl.rst:1293
msgid ""
"This method will raise :exc:`NotImplementedError` if :data:`HAS_ALPN` is "
"False."
msgstr ""
#: ../Doc/library/ssl.rst:1296
msgid ""
"OpenSSL 1.1.0+ will abort the handshake and raise :exc:`SSLError` when both "
"sides support ALPN but cannot agree on a protocol."
msgstr ""
#: ../Doc/library/ssl.rst:1303
msgid ""
"Specify which protocols the socket should advertise during the SSL/TLS "
"handshake. It should be a list of strings, like ``['http/1.1', 'spdy/2']``, "
"ordered by preference. The selection of a protocol will happen during the "
"handshake, and will play out according to the `NPN draft specification "
"<https://tools.ietf.org/html/draft-agl-tls-nextprotoneg>`_. After a "
"successful handshake, the :meth:`SSLSocket.selected_npn_protocol` method "
"will return the agreed-upon protocol."
msgstr ""
#: ../Doc/library/ssl.rst:1311
msgid ""
"This method will raise :exc:`NotImplementedError` if :data:`HAS_NPN` is "
"False."
msgstr ""
#: ../Doc/library/ssl.rst:1318
msgid ""
"Register a callback function that will be called after the TLS Client Hello "
"handshake message has been received by the SSL/TLS server when the TLS "
"client specifies a server name indication. The server name indication "
"mechanism is specified in :rfc:`6066` section 3 - Server Name Indication."
msgstr ""
#: ../Doc/library/ssl.rst:1323
msgid ""
"Only one callback can be set per ``SSLContext``. If *server_name_callback* "
"is ``None`` then the callback is disabled. Calling this function a "
"subsequent time will disable the previously registered callback."
msgstr ""
#: ../Doc/library/ssl.rst:1327
msgid ""
"The callback function, *server_name_callback*, will be called with three "
"arguments; the first being the :class:`ssl.SSLSocket`, the second is a "
"string that represents the server name that the client is intending to "
"communicate (or :const:`None` if the TLS Client Hello does not contain a "
"server name) and the third argument is the original :class:`SSLContext`. The "
"server name argument is the IDNA decoded server name."
msgstr ""
#: ../Doc/library/ssl.rst:1334
msgid ""
"A typical use of this callback is to change the :class:`ssl.SSLSocket`'s :"
"attr:`SSLSocket.context` attribute to a new object of type :class:"
"`SSLContext` representing a certificate chain that matches the server name."
msgstr ""
#: ../Doc/library/ssl.rst:1339
msgid ""
"Due to the early negotiation phase of the TLS connection, only limited "
"methods and attributes are usable like :meth:`SSLSocket."
"selected_alpn_protocol` and :attr:`SSLSocket.context`. :meth:`SSLSocket."
"getpeercert`, :meth:`SSLSocket.getpeercert`, :meth:`SSLSocket.cipher` and :"
"meth:`SSLSocket.compress` methods require that the TLS connection has "
"progressed beyond the TLS Client Hello and therefore will not contain return "
"meaningful values nor can they be called safely."
msgstr ""
#: ../Doc/library/ssl.rst:1347
msgid ""
"The *server_name_callback* function must return ``None`` to allow the TLS "
"negotiation to continue. If a TLS failure is required, a constant :const:"
"`ALERT_DESCRIPTION_* <ALERT_DESCRIPTION_INTERNAL_ERROR>` can be returned. "
"Other return values will result in a TLS fatal error with :const:"
"`ALERT_DESCRIPTION_INTERNAL_ERROR`."
msgstr ""
#: ../Doc/library/ssl.rst:1353
msgid ""
"If there is an IDNA decoding error on the server name, the TLS connection "
"will terminate with an :const:`ALERT_DESCRIPTION_INTERNAL_ERROR` fatal TLS "
"alert message to the client."
msgstr ""
#: ../Doc/library/ssl.rst:1357
msgid ""
"If an exception is raised from the *server_name_callback* function the TLS "
"connection will terminate with a fatal TLS alert message :const:"
"`ALERT_DESCRIPTION_HANDSHAKE_FAILURE`."
msgstr ""
#: ../Doc/library/ssl.rst:1361
msgid ""
"This method will raise :exc:`NotImplementedError` if the OpenSSL library had "
"OPENSSL_NO_TLSEXT defined when it was built."
msgstr ""
#: ../Doc/library/ssl.rst:1368
msgid ""
"Load the key generation parameters for Diffie-Helman (DH) key exchange. "
"Using DH key exchange improves forward secrecy at the expense of "
"computational resources (both on the server and on the client). The *dhfile* "
"parameter should be the path to a file containing DH parameters in PEM "
"format."
msgstr ""
#: ../Doc/library/ssl.rst:1374
msgid ""
"This setting doesn't apply to client sockets. You can also use the :data:"
"`OP_SINGLE_DH_USE` option to further improve security."
msgstr ""
#: ../Doc/library/ssl.rst:1381
msgid ""
"Set the curve name for Elliptic Curve-based Diffie-Hellman (ECDH) key "
"exchange. ECDH is significantly faster than regular DH while arguably as "
"secure. The *curve_name* parameter should be a string describing a well-"
"known elliptic curve, for example ``prime256v1`` for a widely supported "
"curve."
msgstr ""
#: ../Doc/library/ssl.rst:1387
msgid ""
"This setting doesn't apply to client sockets. You can also use the :data:"
"`OP_SINGLE_ECDH_USE` option to further improve security."
msgstr ""
#: ../Doc/library/ssl.rst:1390
msgid "This method is not available if :data:`HAS_ECDH` is ``False``."
msgstr ""
#: ../Doc/library/ssl.rst:1395
msgid ""
"`SSL/TLS & Perfect Forward Secrecy <http://vincent.bernat.im/en/blog/2011-"
"ssl-perfect-forward-secrecy.html>`_"
msgstr ""
#: ../Doc/library/ssl.rst:1396
msgid "Vincent Bernat."
msgstr ""
#: ../Doc/library/ssl.rst:1402
msgid ""
"Wrap an existing Python socket *sock* and return an :class:`SSLSocket` "
"object. *sock* must be a :data:`~socket.SOCK_STREAM` socket; other socket "
"types are unsupported."
msgstr ""
#: ../Doc/library/ssl.rst:1406
msgid ""
"The returned SSL socket is tied to the context, its settings and "
"certificates. The parameters *server_side*, *do_handshake_on_connect* and "
"*suppress_ragged_eofs* have the same meaning as in the top-level :func:"
"`wrap_socket` function."
msgstr ""
#: ../Doc/library/ssl.rst:1411
msgid ""
"On client connections, the optional parameter *server_hostname* specifies "
"the hostname of the service which we are connecting to. This allows a "
"single server to host multiple SSL-based services with distinct "
"certificates, quite similarly to HTTP virtual hosts. Specifying "
"*server_hostname* will raise a :exc:`ValueError` if *server_side* is true."
msgstr ""
#: ../Doc/library/ssl.rst:1417
msgid ""
"Always allow a server_hostname to be passed, even if OpenSSL does not have "
"SNI."
msgstr ""
#: ../Doc/library/ssl.rst:1424
msgid ""
"Create a new :class:`SSLObject` instance by wrapping the BIO objects "
"*incoming* and *outgoing*. The SSL routines will read input data from the "
"incoming BIO and write data to the outgoing BIO."
msgstr ""
#: ../Doc/library/ssl.rst:1428
msgid ""
"The *server_side* and *server_hostname* parameters have the same meaning as "
"in :meth:`SSLContext.wrap_socket`."
msgstr ""
#: ../Doc/library/ssl.rst:1433
msgid ""
"Get statistics about the SSL sessions created or managed by this context. A "
"dictionary is returned which maps the names of each `piece of information "
"<https://www.openssl.org/docs/ssl/SSL_CTX_sess_number.html>`_ to their "
"numeric values. For example, here is the total number of hits and misses in "
"the session cache since the context was created::"
msgstr ""
#: ../Doc/library/ssl.rst:1445
msgid ""
"Whether to match the peer cert's hostname with :func:`match_hostname` in :"
"meth:`SSLSocket.do_handshake`. The context's :attr:`~SSLContext.verify_mode` "
"must be set to :data:`CERT_OPTIONAL` or :data:`CERT_REQUIRED`, and you must "
"pass *server_hostname* to :meth:`~SSLContext.wrap_socket` in order to match "
"the hostname."
msgstr ""
#: ../Doc/library/ssl.rst:1468
msgid "This features requires OpenSSL 0.9.8f or newer."
msgstr ""
#: ../Doc/library/ssl.rst:1472
msgid ""
"An integer representing the set of SSL options enabled on this context. The "
"default value is :data:`OP_ALL`, but you can specify other options such as :"
"data:`OP_NO_SSLv2` by ORing them together."
msgstr ""
#: ../Doc/library/ssl.rst:1477
msgid ""
"With versions of OpenSSL older than 0.9.8m, it is only possible to set "
"options, not to clear them. Attempting to clear an option (by resetting the "
"corresponding bits) will raise a ``ValueError``."
msgstr ""
#: ../Doc/library/ssl.rst:1483
msgid ""
"The protocol version chosen when constructing the context. This attribute "
"is read-only."
msgstr ""
#: ../Doc/library/ssl.rst:1488
msgid ""
"The flags for certificate verification operations. You can set flags like :"
"data:`VERIFY_CRL_CHECK_LEAF` by ORing them together. By default OpenSSL does "
"neither require nor verify certificate revocation lists (CRLs). Available "
"only with openssl version 0.9.8+."
msgstr ""
#: ../Doc/library/ssl.rst:1497
msgid ""
"Whether to try to verify other peers' certificates and how to behave if "
"verification fails. This attribute must be one of :data:`CERT_NONE`, :data:"
"`CERT_OPTIONAL` or :data:`CERT_REQUIRED`."
msgstr ""
#: ../Doc/library/ssl.rst:1509
msgid "Certificates"
msgstr ""
#: ../Doc/library/ssl.rst:1511
msgid ""
"Certificates in general are part of a public-key / private-key system. In "
"this system, each *principal*, (which may be a machine, or a person, or an "
"organization) is assigned a unique two-part encryption key. One part of the "
"key is public, and is called the *public key*; the other part is kept "
"secret, and is called the *private key*. The two parts are related, in that "
"if you encrypt a message with one of the parts, you can decrypt it with the "
"other part, and **only** with the other part."
msgstr ""
#: ../Doc/library/ssl.rst:1519
msgid ""
"A certificate contains information about two principals. It contains the "
"name of a *subject*, and the subject's public key. It also contains a "
"statement by a second principal, the *issuer*, that the subject is who he "
"claims to be, and that this is indeed the subject's public key. The "
"issuer's statement is signed with the issuer's private key, which only the "
"issuer knows. However, anyone can verify the issuer's statement by finding "
"the issuer's public key, decrypting the statement with it, and comparing it "
"to the other information in the certificate. The certificate also contains "
"information about the time period over which it is valid. This is expressed "
"as two fields, called \"notBefore\" and \"notAfter\"."
msgstr ""
#: ../Doc/library/ssl.rst:1529
msgid ""
"In the Python use of certificates, a client or server can use a certificate "
"to prove who they are. The other side of a network connection can also be "
"required to produce a certificate, and that certificate can be validated to "
"the satisfaction of the client or server that requires such validation. The "
"connection attempt can be set to raise an exception if the validation fails. "
"Validation is done automatically, by the underlying OpenSSL framework; the "
"application need not concern itself with its mechanics. But the application "
"does usually need to provide sets of certificates to allow this process to "
"take place."
msgstr ""
#: ../Doc/library/ssl.rst:1539
msgid ""
"Python uses files to contain certificates. They should be formatted as \"PEM"
"\" (see :rfc:`1422`), which is a base-64 encoded form wrapped with a header "
"line and a footer line::"
msgstr ""
#: ../Doc/library/ssl.rst:1548
msgid "Certificate chains"
msgstr ""
#: ../Doc/library/ssl.rst:1550
msgid ""
"The Python files which contain certificates can contain a sequence of "
"certificates, sometimes called a *certificate chain*. This chain should "
"start with the specific certificate for the principal who \"is\" the client "
"or server, and then the certificate for the issuer of that certificate, and "
"then the certificate for the issuer of *that* certificate, and so on up the "
"chain till you get to a certificate which is *self-signed*, that is, a "
"certificate which has the same subject and issuer, sometimes called a *root "
"certificate*. The certificates should just be concatenated together in the "
"certificate file. For example, suppose we had a three certificate chain, "
"from our server certificate to the certificate of the certification "
"authority that signed our server certificate, to the root certificate of the "
"agency which issued the certification authority's certificate::"
msgstr ""
#: ../Doc/library/ssl.rst:1574
msgid "CA certificates"
msgstr ""
#: ../Doc/library/ssl.rst:1576
msgid ""
"If you are going to require validation of the other side of the connection's "
"certificate, you need to provide a \"CA certs\" file, filled with the "
"certificate chains for each issuer you are willing to trust. Again, this "
"file just contains these chains concatenated together. For validation, "
"Python will use the first chain it finds in the file which matches. The "
"platform's certificates file can be used by calling :meth:`SSLContext."
"load_default_certs`, this is done automatically with :func:`."
"create_default_context`."
msgstr ""
#: ../Doc/library/ssl.rst:1585
msgid "Combined key and certificate"
msgstr ""
#: ../Doc/library/ssl.rst:1587
msgid ""
"Often the private key is stored in the same file as the certificate; in this "
"case, only the ``certfile`` parameter to :meth:`SSLContext.load_cert_chain` "
"and :func:`wrap_socket` needs to be passed. If the private key is stored "
"with the certificate, it should come before the first certificate in the "
"certificate chain::"
msgstr ""
#: ../Doc/library/ssl.rst:1601
msgid "Self-signed certificates"
msgstr ""
#: ../Doc/library/ssl.rst:1603
msgid ""
"If you are going to create a server that provides SSL-encrypted connection "
"services, you will need to acquire a certificate for that service. There "
"are many ways of acquiring appropriate certificates, such as buying one from "
"a certification authority. Another common practice is to generate a self-"
"signed certificate. The simplest way to do this is with the OpenSSL "
"package, using something like the following::"
msgstr ""
#: ../Doc/library/ssl.rst:1632
msgid ""
"The disadvantage of a self-signed certificate is that it is its own root "
"certificate, and no one else will have it in their cache of known (and "
"trusted) root certificates."
msgstr ""
#: ../Doc/library/ssl.rst:1638
msgid "Examples"
msgstr "Exemples"
#: ../Doc/library/ssl.rst:1641
msgid "Testing for SSL support"
msgstr ""
#: ../Doc/library/ssl.rst:1643
msgid ""
"To test for the presence of SSL support in a Python installation, user code "
"should use the following idiom::"
msgstr ""
#: ../Doc/library/ssl.rst:1654
msgid "Client-side operation"
msgstr ""
#: ../Doc/library/ssl.rst:1656
msgid ""
"This example creates a SSL context with the recommended security settings "
"for client sockets, including automatic certificate verification::"
msgstr ""
#: ../Doc/library/ssl.rst:1661
msgid ""
"If you prefer to tune security settings yourself, you might create a context "
"from scratch (but beware that you might not get the settings right)::"
msgstr ""
#: ../Doc/library/ssl.rst:1670
msgid ""
"(this snippet assumes your operating system places a bundle of all CA "
"certificates in ``/etc/ssl/certs/ca-bundle.crt``; if not, you'll get an "
"error and have to adjust the location)"
msgstr ""
#: ../Doc/library/ssl.rst:1674
msgid ""
"When you use the context to connect to a server, :const:`CERT_REQUIRED` "
"validates the server certificate: it ensures that the server certificate was "
"signed with one of the CA certificates, and checks the signature for "
"correctness::"
msgstr ""
#: ../Doc/library/ssl.rst:1683
msgid "You may then fetch the certificate::"
msgstr ""
#: ../Doc/library/ssl.rst:1687
msgid ""
"Visual inspection shows that the certificate does identify the desired "
"service (that is, the HTTPS host ``www.python.org``)::"
msgstr ""
#: ../Doc/library/ssl.rst:1730
msgid ""
"Now the SSL channel is established and the certificate verified, you can "
"proceed to talk with the server::"
msgstr ""
#: ../Doc/library/ssl.rst:1757
msgid "Server-side operation"
msgstr ""
#: ../Doc/library/ssl.rst:1759
msgid ""
"For server operation, typically you'll need to have a server certificate, "
"and private key, each in a file. You'll first create a context holding the "
"key and the certificate, so that clients can check your authenticity. Then "
"you'll open a socket, bind it to a port, call :meth:`listen` on it, and "
"start waiting for clients to connect::"
msgstr ""
#: ../Doc/library/ssl.rst:1774
msgid ""
"When a client connects, you'll call :meth:`accept` on the socket to get the "
"new socket from the other end, and use the context's :meth:`SSLContext."
"wrap_socket` method to create a server-side SSL socket for the connection::"
msgstr ""
#: ../Doc/library/ssl.rst:1787
msgid ""
"Then you'll read data from the ``connstream`` and do something with it till "
"you are finished with the client (or the client is finished with you)::"
msgstr ""
#: ../Doc/library/ssl.rst:1801
msgid ""
"And go back to listening for new client connections (of course, a real "
"server would probably handle each client connection in a separate thread, or "
"put the sockets in :ref:`non-blocking mode <ssl-nonblocking>` and use an "
"event loop)."
msgstr ""
#: ../Doc/library/ssl.rst:1809
msgid "Notes on non-blocking sockets"
msgstr ""
#: ../Doc/library/ssl.rst:1811
msgid ""
"SSL sockets behave slightly different than regular sockets in non-blocking "
"mode. When working with non-blocking sockets, there are thus several things "
"you need to be aware of:"
msgstr ""
#: ../Doc/library/ssl.rst:1815
msgid ""
"Most :class:`SSLSocket` methods will raise either :exc:`SSLWantWriteError` "
"or :exc:`SSLWantReadError` instead of :exc:`BlockingIOError` if an I/O "
"operation would block. :exc:`SSLWantReadError` will be raised if a read "
"operation on the underlying socket is necessary, and :exc:"
"`SSLWantWriteError` for a write operation on the underlying socket. Note "
"that attempts to *write* to an SSL socket may require *reading* from the "
"underlying socket first, and attempts to *read* from the SSL socket may "
"require a prior *write* to the underlying socket."
msgstr ""
#: ../Doc/library/ssl.rst:1827
msgid ""
"In earlier Python versions, the :meth:`!SSLSocket.send` method returned zero "
"instead of raising :exc:`SSLWantWriteError` or :exc:`SSLWantReadError`."
msgstr ""
#: ../Doc/library/ssl.rst:1831
msgid ""
"Calling :func:`~select.select` tells you that the OS-level socket can be "
"read from (or written to), but it does not imply that there is sufficient "
"data at the upper SSL layer. For example, only part of an SSL frame might "
"have arrived. Therefore, you must be ready to handle :meth:`SSLSocket.recv` "
"and :meth:`SSLSocket.send` failures, and retry after another call to :func:"
"`~select.select`."
msgstr ""
#: ../Doc/library/ssl.rst:1838
msgid ""
"Conversely, since the SSL layer has its own framing, a SSL socket may still "
"have data available for reading without :func:`~select.select` being aware "
"of it. Therefore, you should first call :meth:`SSLSocket.recv` to drain any "
"potentially available data, and then only block on a :func:`~select.select` "
"call if still necessary."
msgstr ""
#: ../Doc/library/ssl.rst:1844
msgid ""
"(of course, similar provisions apply when using other primitives such as :"
"func:`~select.poll`, or those in the :mod:`selectors` module)"
msgstr ""
#: ../Doc/library/ssl.rst:1847
msgid ""
"The SSL handshake itself will be non-blocking: the :meth:`SSLSocket."
"do_handshake` method has to be retried until it returns successfully. Here "
"is a synopsis using :func:`~select.select` to wait for the socket's "
"readiness::"
msgstr ""
#: ../Doc/library/ssl.rst:1863
msgid ""
"The :mod:`asyncio` module supports :ref:`non-blocking SSL sockets <ssl-"
"nonblocking>` and provides a higher level API. It polls for events using "
"the :mod:`selectors` module and handles :exc:`SSLWantWriteError`, :exc:"
"`SSLWantReadError` and :exc:`BlockingIOError` exceptions. It runs the SSL "
"handshake asynchronously as well."
msgstr ""
#: ../Doc/library/ssl.rst:1872
msgid "Memory BIO Support"
msgstr ""
#: ../Doc/library/ssl.rst:1876
msgid ""
"Ever since the SSL module was introduced in Python 2.6, the :class:"
"`SSLSocket` class has provided two related but distinct areas of "
"functionality:"
msgstr ""
#: ../Doc/library/ssl.rst:1879
msgid "SSL protocol handling"
msgstr ""
#: ../Doc/library/ssl.rst:1880
msgid "Network IO"
msgstr ""
#: ../Doc/library/ssl.rst:1882
msgid ""
"The network IO API is identical to that provided by :class:`socket.socket`, "
"from which :class:`SSLSocket` also inherits. This allows an SSL socket to be "
"used as a drop-in replacement for a regular socket, making it very easy to "
"add SSL support to an existing application."
msgstr ""
#: ../Doc/library/ssl.rst:1887
msgid ""
"Combining SSL protocol handling and network IO usually works well, but there "
"are some cases where it doesn't. An example is async IO frameworks that want "
"to use a different IO multiplexing model than the \"select/poll on a file "
"descriptor\" (readiness based) model that is assumed by :class:`socket."
"socket` and by the internal OpenSSL socket IO routines. This is mostly "
"relevant for platforms like Windows where this model is not efficient. For "
"this purpose, a reduced scope variant of :class:`SSLSocket` called :class:"
"`SSLObject` is provided."
msgstr ""
#: ../Doc/library/ssl.rst:1898
msgid ""
"A reduced-scope variant of :class:`SSLSocket` representing an SSL protocol "
"instance that does not contain any network IO methods. This class is "
"typically used by framework authors that want to implement asynchronous IO "
"for SSL through memory buffers."
msgstr ""
#: ../Doc/library/ssl.rst:1903
msgid ""
"This class implements an interface on top of a low-level SSL object as "
"implemented by OpenSSL. This object captures the state of an SSL connection "
"but does not provide any network IO itself. IO needs to be performed through "
"separate \"BIO\" objects which are OpenSSL's IO abstraction layer."
msgstr ""
#: ../Doc/library/ssl.rst:1908
msgid ""
"An :class:`SSLObject` instance can be created using the :meth:`~SSLContext."
"wrap_bio` method. This method will create the :class:`SSLObject` instance "
"and bind it to a pair of BIOs. The *incoming* BIO is used to pass data from "
"Python to the SSL protocol instance, while the *outgoing* BIO is used to "
"pass data the other way around."
msgstr ""
#: ../Doc/library/ssl.rst:1914
msgid "The following methods are available:"
msgstr ""
#: ../Doc/library/ssl.rst:1916
msgid ":attr:`~SSLSocket.context`"
msgstr ""
#: ../Doc/library/ssl.rst:1917
msgid ":attr:`~SSLSocket.server_side`"
msgstr ""
#: ../Doc/library/ssl.rst:1918
msgid ":attr:`~SSLSocket.server_hostname`"
msgstr ""
#: ../Doc/library/ssl.rst:1919
msgid ":meth:`~SSLSocket.read`"
msgstr ""
#: ../Doc/library/ssl.rst:1920
msgid ":meth:`~SSLSocket.write`"
msgstr ""
#: ../Doc/library/ssl.rst:1921
msgid ":meth:`~SSLSocket.getpeercert`"
msgstr ""
#: ../Doc/library/ssl.rst:1922
msgid ":meth:`~SSLSocket.selected_npn_protocol`"
msgstr ""
#: ../Doc/library/ssl.rst:1923
msgid ":meth:`~SSLSocket.cipher`"
msgstr ""
#: ../Doc/library/ssl.rst:1924
msgid ":meth:`~SSLSocket.shared_ciphers`"
msgstr ""
#: ../Doc/library/ssl.rst:1925
msgid ":meth:`~SSLSocket.compression`"
msgstr ""
#: ../Doc/library/ssl.rst:1926
msgid ":meth:`~SSLSocket.pending`"
msgstr ""
#: ../Doc/library/ssl.rst:1927
msgid ":meth:`~SSLSocket.do_handshake`"
msgstr ""
#: ../Doc/library/ssl.rst:1928
msgid ":meth:`~SSLSocket.unwrap`"
msgstr ""
#: ../Doc/library/ssl.rst:1929
msgid ":meth:`~SSLSocket.get_channel_binding`"
msgstr ""
#: ../Doc/library/ssl.rst:1931
msgid ""
"When compared to :class:`SSLSocket`, this object lacks the following "
"features:"
msgstr ""
#: ../Doc/library/ssl.rst:1934
msgid ""
"Any form of network IO incluging methods such as ``recv()`` and ``send()``."
msgstr ""
#: ../Doc/library/ssl.rst:1937
msgid ""
"There is no *do_handshake_on_connect* machinery. You must always manually "
"call :meth:`~SSLSocket.do_handshake` to start the handshake."
msgstr ""
#: ../Doc/library/ssl.rst:1940
msgid ""
"There is no handling of *suppress_ragged_eofs*. All end-of-file conditions "
"that are in violation of the protocol are reported via the :exc:"
"`SSLEOFError` exception."
msgstr ""
#: ../Doc/library/ssl.rst:1944
msgid ""
"The method :meth:`~SSLSocket.unwrap` call does not return anything, unlike "
"for an SSL socket where it returns the underlying socket."
msgstr ""
#: ../Doc/library/ssl.rst:1947
msgid ""
"The *server_name_callback* callback passed to :meth:`SSLContext."
"set_servername_callback` will get an :class:`SSLObject` instance instead of "
"a :class:`SSLSocket` instance as its first parameter."
msgstr ""
#: ../Doc/library/ssl.rst:1951
msgid "Some notes related to the use of :class:`SSLObject`:"
msgstr ""
#: ../Doc/library/ssl.rst:1953
msgid ""
"All IO on an :class:`SSLObject` is :ref:`non-blocking <ssl-nonblocking>`. "
"This means that for example :meth:`~SSLSocket.read` will raise an :exc:"
"`SSLWantReadError` if it needs more data than the incoming BIO has available."
msgstr ""
#: ../Doc/library/ssl.rst:1958
msgid ""
"There is no module-level ``wrap_bio()`` call like there is for :meth:"
"`~SSLContext.wrap_socket`. An :class:`SSLObject` is always created via an :"
"class:`SSLContext`."
msgstr ""
#: ../Doc/library/ssl.rst:1962
msgid ""
"An SSLObject communicates with the outside world using memory buffers. The "
"class :class:`MemoryBIO` provides a memory buffer that can be used for this "
"purpose. It wraps an OpenSSL memory BIO (Basic IO) object:"
msgstr ""
#: ../Doc/library/ssl.rst:1968
msgid ""
"A memory buffer that can be used to pass data between Python and an SSL "
"protocol instance."
msgstr ""
#: ../Doc/library/ssl.rst:1973
msgid "Return the number of bytes currently in the memory buffer."
msgstr ""
#: ../Doc/library/ssl.rst:1977
msgid ""
"A boolean indicating whether the memory BIO is current at the end-of-file "
"position."
msgstr ""
#: ../Doc/library/ssl.rst:1982
msgid ""
"Read up to *n* bytes from the memory buffer. If *n* is not specified or "
"negative, all bytes are returned."
msgstr ""
#: ../Doc/library/ssl.rst:1987
msgid ""
"Write the bytes from *buf* to the memory BIO. The *buf* argument must be an "
"object supporting the buffer protocol."
msgstr ""
#: ../Doc/library/ssl.rst:1990
msgid ""
"The return value is the number of bytes written, which is always equal to "
"the length of *buf*."
msgstr ""
#: ../Doc/library/ssl.rst:1995
msgid ""
"Write an EOF marker to the memory BIO. After this method has been called, it "
"is illegal to call :meth:`~MemoryBIO.write`. The attribute :attr:`eof` will "
"become true after all data currently in the buffer has been read."
msgstr ""
#: ../Doc/library/ssl.rst:2003
msgid "Security considerations"
msgstr ""
#: ../Doc/library/ssl.rst:2006
msgid "Best defaults"
msgstr ""
#: ../Doc/library/ssl.rst:2008
msgid ""
"For **client use**, if you don't have any special requirements for your "
"security policy, it is highly recommended that you use the :func:"
"`create_default_context` function to create your SSL context. It will load "
"the system's trusted CA certificates, enable certificate validation and "
"hostname checking, and try to choose reasonably secure protocol and cipher "
"settings."
msgstr ""
#: ../Doc/library/ssl.rst:2015
msgid ""
"For example, here is how you would use the :class:`smtplib.SMTP` class to "
"create a trusted, secure connection to a SMTP server::"
msgstr ""
#: ../Doc/library/ssl.rst:2024
msgid ""
"If a client certificate is needed for the connection, it can be added with :"
"meth:`SSLContext.load_cert_chain`."
msgstr ""
#: ../Doc/library/ssl.rst:2027
msgid ""
"By contrast, if you create the SSL context by calling the :class:"
"`SSLContext` constructor yourself, it will not have certificate validation "
"nor hostname checking enabled by default. If you do so, please read the "
"paragraphs below to achieve a good security level."
msgstr ""
#: ../Doc/library/ssl.rst:2033
msgid "Manual settings"
msgstr ""
#: ../Doc/library/ssl.rst:2036
msgid "Verifying certificates"
msgstr ""
#: ../Doc/library/ssl.rst:2038
msgid ""
"When calling the :class:`SSLContext` constructor directly, :const:"
"`CERT_NONE` is the default. Since it does not authenticate the other peer, "
"it can be insecure, especially in client mode where most of time you would "
"like to ensure the authenticity of the server you're talking to. Therefore, "
"when in client mode, it is highly recommended to use :const:"
"`CERT_REQUIRED`. However, it is in itself not sufficient; you also have to "
"check that the server certificate, which can be obtained by calling :meth:"
"`SSLSocket.getpeercert`, matches the desired service. For many protocols "
"and applications, the service can be identified by the hostname; in this "
"case, the :func:`match_hostname` function can be used. This common check is "
"automatically performed when :attr:`SSLContext.check_hostname` is enabled."
msgstr ""
#: ../Doc/library/ssl.rst:2051
msgid ""
"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 "
"have to specify :const:`CERT_REQUIRED` and similarly check the client "
"certificate."
msgstr ""
#: ../Doc/library/ssl.rst:2057
msgid ""
"In client mode, :const:`CERT_OPTIONAL` and :const:`CERT_REQUIRED` are "
"equivalent unless anonymous ciphers are enabled (they are disabled by "
"default)."
msgstr ""
#: ../Doc/library/ssl.rst:2062
msgid "Protocol versions"
msgstr ""
#: ../Doc/library/ssl.rst:2064
msgid ""
"SSL versions 2 and 3 are considered insecure and are therefore dangerous to "
"use. If you want maximum compatibility between clients and servers, it is "
"recommended to use :const:`PROTOCOL_TLS` as the protocol version and then "
"disable SSLv2 and SSLv3 explicitly using the :data:`SSLContext.options` "
"attribute::"
msgstr ""
#: ../Doc/library/ssl.rst:2076
msgid ""
"The SSL context created above will only allow TLSv1.2 and later (if "
"supported by your system) connections."
msgstr ""
#: ../Doc/library/ssl.rst:2080
msgid "Cipher selection"
msgstr ""
#: ../Doc/library/ssl.rst:2082
msgid ""
"If you have advanced security requirements, fine-tuning of the ciphers "
"enabled when negotiating a SSL session is possible through the :meth:"
"`SSLContext.set_ciphers` method. Starting from Python 3.2.3, the ssl module "
"disables certain weak ciphers by default, but you may want to further "
"restrict the cipher choice. Be sure to read OpenSSL's documentation about "
"the `cipher list format <https://www.openssl.org/docs/apps/ciphers."
"html#CIPHER-LIST-FORMAT>`_. If you want to check which ciphers are enabled "
"by a given cipher list, use the ``openssl ciphers`` command on your system."
msgstr ""
#: ../Doc/library/ssl.rst:2092
msgid "Multi-processing"
msgstr ""
#: ../Doc/library/ssl.rst:2094
msgid ""
"If using this module as part of a multi-processed application (using, for "
"example the :mod:`multiprocessing` or :mod:`concurrent.futures` modules), be "
"aware that OpenSSL's internal random number generator does not properly "
"handle forked processes. Applications must change the PRNG state of the "
"parent process if they use any SSL feature with :func:`os.fork`. Any "
"successful call of :func:`~ssl.RAND_add`, :func:`~ssl.RAND_bytes` or :func:"
"`~ssl.RAND_pseudo_bytes` is sufficient."
msgstr ""
#: ../Doc/library/ssl.rst:2106
msgid "Class :class:`socket.socket`"
msgstr ""
#: ../Doc/library/ssl.rst:2106
msgid "Documentation of underlying :mod:`socket` class"
msgstr ""
#: ../Doc/library/ssl.rst:2109
msgid ""
"`SSL/TLS Strong Encryption: An Introduction <https://httpd.apache.org/docs/"
"trunk/en/ssl/ssl_intro.html>`_"
msgstr ""
#: ../Doc/library/ssl.rst:2109
msgid "Intro from the Apache webserver documentation"
msgstr ""
#: ../Doc/library/ssl.rst:2112
msgid ""
"`RFC 1422: Privacy Enhancement for Internet Electronic Mail: Part II: "
"Certificate-Based Key Management <https://www.ietf.org/rfc/rfc1422>`_"
msgstr ""
#: ../Doc/library/ssl.rst:2112
msgid "Steve Kent"
msgstr ""
#: ../Doc/library/ssl.rst:2115
msgid ""
"`RFC 1750: Randomness Recommendations for Security <https://www.ietf.org/rfc/"
"rfc1750>`_"
msgstr ""
#: ../Doc/library/ssl.rst:2115
msgid "D. Eastlake et. al."
msgstr ""
#: ../Doc/library/ssl.rst:2118
msgid ""
"`RFC 3280: Internet X.509 Public Key Infrastructure Certificate and CRL "
"Profile <https://www.ietf.org/rfc/rfc3280>`_"
msgstr ""
#: ../Doc/library/ssl.rst:2118
msgid "Housley et. al."
msgstr ""
#: ../Doc/library/ssl.rst:2121
msgid ""
"`RFC 4366: Transport Layer Security (TLS) Extensions <https://www.ietf.org/"
"rfc/rfc4366>`_"
msgstr ""
#: ../Doc/library/ssl.rst:2121
msgid "Blake-Wilson et. al."
msgstr ""
#: ../Doc/library/ssl.rst:2124
msgid ""
"`RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 <https://"
"tools.ietf.org/html/rfc5246>`_"
msgstr ""
#: ../Doc/library/ssl.rst:2124
msgid "T. Dierks et. al."
msgstr ""
#: ../Doc/library/ssl.rst:2127
msgid ""
"`RFC 6066: Transport Layer Security (TLS) Extensions <https://tools.ietf.org/"
"html/rfc6066>`_"
msgstr ""
#: ../Doc/library/ssl.rst:2127
msgid "D. Eastlake"
msgstr ""
#: ../Doc/library/ssl.rst:2129
msgid ""
"`IANA TLS: Transport Layer Security (TLS) Parameters <https://www.iana.org/"
"assignments/tls-parameters/tls-parameters.xml>`_"
msgstr ""
#: ../Doc/library/ssl.rst:2130
msgid "IANA"
msgstr ""