diff options
author | Victor Stinner <vstinner@python.org> | 2022-06-24 09:05:53 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-06-24 09:05:53 (GMT) |
commit | d435a18c537a62a89a70005885e6e09f58997d8a (patch) | |
tree | e75b29c5d7932475dc06e9c6eed13b8d47dabdb4 /Doc/library/ssl.rst | |
parent | 6e33ba114ffb47505fec59674c5cce5eb6476f76 (diff) | |
download | cpython-d435a18c537a62a89a70005885e6e09f58997d8a.zip cpython-d435a18c537a62a89a70005885e6e09f58997d8a.tar.gz cpython-d435a18c537a62a89a70005885e6e09f58997d8a.tar.bz2 |
gh-94199: Remove ssl.RAND_pseudo_bytes() function (#94202)
Remove the ssl.RAND_pseudo_bytes() function, deprecated in Python
3.6: use os.urandom() or ssl.RAND_bytes() instead.
Diffstat (limited to 'Doc/library/ssl.rst')
-rw-r--r-- | Doc/library/ssl.rst | 25 |
1 files changed, 2 insertions, 23 deletions
diff --git a/Doc/library/ssl.rst b/Doc/library/ssl.rst index 7e26e2e..8df64ff 100644 --- a/Doc/library/ssl.rst +++ b/Doc/library/ssl.rst @@ -311,27 +311,6 @@ Random generation .. versionadded:: 3.3 -.. function:: RAND_pseudo_bytes(num) - - 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. - - 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. - - For almost all applications :func:`os.urandom` is preferable. - - .. versionadded:: 3.3 - - .. deprecated:: 3.6 - - OpenSSL has deprecated :func:`ssl.RAND_pseudo_bytes`, use - :func:`ssl.RAND_bytes` instead. - .. function:: RAND_status() Return ``True`` if the SSL pseudo-random number generator has been seeded @@ -2717,8 +2696,8 @@ 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. +successful call of :func:`~ssl.RAND_add` or :func:`~ssl.RAND_bytes` is +sufficient. .. _ssl-tlsv1_3: |