cryptography 40.0.2__tar.gz → 41.0.1__tar.gz

{cryptography-40.0.2 → cryptography-41.0.1}/CHANGELOG.rst

@@ -1,12 +1,50 @@
 Changelog
 =========
 
+.. _v41-0-1:
+
+41.0.1 - 2023-06-01
+~~~~~~~~~~~~~~~~~~~
+
+* Temporarily allow invalid ECDSA signature algorithm parameters in X.509
+  certificates, which are generated by older versions of Java.
+* Allow null bytes in pass phrases when serializing private keys.
+
+.. _v41-0-0:
+
+41.0.0 - 2023-05-30
+~~~~~~~~~~~~~~~~~~~
+
+* **BACKWARDS INCOMPATIBLE:** Support for OpenSSL less than 1.1.1d has been
+  removed.  Users on older version of OpenSSL will need to upgrade.
+* **BACKWARDS INCOMPATIBLE:** Support for Python 3.6 has been removed.
+* **BACKWARDS INCOMPATIBLE:** Dropped support for LibreSSL < 3.6.
+* Updated the minimum supported Rust version (MSRV) to 1.56.0, from 1.48.0.
+* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.1.1.
+* Added support for the :class:`~cryptography.x509.OCSPAcceptableResponses`
+  OCSP extension.
+* Added support for the :class:`~cryptography.x509.MSCertificateTemplate`
+  proprietary Microsoft certificate extension.
+* Implemented support for equality checks on all asymmetric public key types.
+* Added support for ``aes256-gcm@openssh.com`` encrypted keys in
+  :func:`~cryptography.hazmat.primitives.serialization.load_ssh_private_key`.
+* Added support for obtaining X.509 certificate signature algorithm parameters
+  (including PSS) via
+  :meth:`~cryptography.x509.Certificate.signature_algorithm_parameters`.
+* Support signing :class:`~cryptography.hazmat.primitives.asymmetric.padding.PSS`
+  X.509 certificates via the new keyword-only argument ``rsa_padding`` on
+  :meth:`~cryptography.x509.CertificateBuilder.sign`.
+* Added support for
+  :class:`~cryptography.hazmat.primitives.ciphers.aead.ChaCha20Poly1305`
+  on BoringSSL.
+
 .. _v40-0-2:
 
 40.0.2 - 2023-04-14
 ~~~~~~~~~~~~~~~~~~~
 
 * Fixed compilation when using LibreSSL 3.7.2.
+* Added some functions to support an upcoming ``pyOpenSSL`` release.
 
 .. _v40-0-1:
 
@@ -21,6 +59,7 @@ Changelog
 40.0.0 - 2023-03-24
 ~~~~~~~~~~~~~~~~~~~
 
+
 * **BACKWARDS INCOMPATIBLE:** As announced in the 39.0.0 changelog, the way
   ``cryptography`` links OpenSSL has changed. This only impacts users who
   build ``cryptography`` from source (i.e., not from a ``wheel``), and
@@ -1772,16 +1811,16 @@ Changelog
   ``no-comp`` (``OPENSSL_NO_COMP``) option.
 * Support :attr:`~cryptography.hazmat.primitives.serialization.Encoding.DER`
   serialization of public keys using the ``public_bytes`` method of
-  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKeyWithSerialization`,
-  :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPublicKeyWithSerialization`,
+  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKey`,
+  :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPublicKey`,
   and
-  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKeyWithSerialization`.
+  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey`.
 * Support :attr:`~cryptography.hazmat.primitives.serialization.Encoding.DER`
   serialization of private keys using the ``private_bytes`` method of
-  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateKeyWithSerialization`,
-  :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPrivateKeyWithSerialization`,
+  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateKey`,
+  :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPrivateKey`,
   and
-  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKeyWithSerialization`.
+  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKey`.
 * Add support for parsing X.509 certificate signing requests (CSRs) with
   :func:`~cryptography.x509.load_pem_x509_csr` and
   :func:`~cryptography.x509.load_der_x509_csr`.
@@ -1854,42 +1893,32 @@ Changelog
   and :func:`~cryptography.hazmat.primitives.serialization.load_der_public_key`
   now support PKCS1 RSA public keys (in addition to the previous support for
   SubjectPublicKeyInfo format for RSA, EC, and DSA).
-* Added
-  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKeyWithSerialization`
-  and deprecated ``EllipticCurvePrivateKeyWithNumbers``.
+* Added ``EllipticCurvePrivateKeyWithSerialization`` and deprecated
+  ``EllipticCurvePrivateKeyWithNumbers``.
 * Added
   :meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKey.private_bytes`
   to
   :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKey`.
-* Added
-  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateKeyWithSerialization`
-  and deprecated ``RSAPrivateKeyWithNumbers``.
+* Added ``RSAPrivateKeyWithSerialization`` and deprecated ``RSAPrivateKeyWithNumbers``.
 * Added
   :meth:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateKey.private_bytes`
   to
   :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateKey`.
-* Added
-  :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPrivateKeyWithSerialization`
-  and deprecated ``DSAPrivateKeyWithNumbers``.
+* Added ``DSAPrivateKeyWithSerialization`` and deprecated ``DSAPrivateKeyWithNumbers``.
 * Added
   :meth:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPrivateKey.private_bytes`
   to
   :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPrivateKey`.
-* Added
-  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKeyWithSerialization`
-  and deprecated ``RSAPublicKeyWithNumbers``.
+* Added ``RSAPublicKeyWithSerialization`` and deprecated ``RSAPublicKeyWithNumbers``.
 * Added ``public_bytes`` to
-  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKeyWithSerialization`.
-* Added
-  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKeyWithSerialization`
-  and deprecated ``EllipticCurvePublicKeyWithNumbers``.
+  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKey`.
+* Added ``EllipticCurvePublicKeyWithSerialization`` and deprecated
+  ``EllipticCurvePublicKeyWithNumbers``.
 * Added ``public_bytes`` to
-  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKeyWithSerialization`.
-* Added
-  :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPublicKeyWithSerialization`
-  and deprecated ``DSAPublicKeyWithNumbers``.
+  :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey`.
+* Added ``DSAPublicKeyWithSerialization`` and deprecated ``DSAPublicKeyWithNumbers``.
 * Added ``public_bytes`` to
-  :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPublicKeyWithSerialization`.
+  :class:`~cryptography.hazmat.primitives.asymmetric.dsa.DSAPublicKey`.
 * :class:`~cryptography.hazmat.primitives.hashes.HashAlgorithm` and
   :class:`~cryptography.hazmat.primitives.hashes.HashContext` were moved from
   ``cryptography.hazmat.primitives.interfaces`` to

{cryptography-40.0.2 → cryptography-41.0.1}/LICENSE

@@ -1,6 +1,3 @@
 This software is made available under the terms of *either* of the licenses
 found in LICENSE.APACHE or LICENSE.BSD. Contributions to cryptography are made
 under the terms of *both* these licenses.
-
-The code used in the OS random engine is derived from CPython, and is licensed
-under the terms of the PSF License Agreement.

{cryptography-40.0.2 → cryptography-41.0.1}/MANIFEST.in

@@ -3,9 +3,8 @@ include CONTRIBUTING.rst
 include LICENSE
 include LICENSE.APACHE
 include LICENSE.BSD
-include LICENSE.PSF
 include README.rst
-include tox.ini
+include noxfile.py
 
 include pyproject.toml
 recursive-include src py.typed *.pyi
@@ -17,6 +16,8 @@ prune docs/_build
 recursive-include tests *.py
 exclude vectors
 recursive-exclude vectors *
+exclude src/rust/target
+recursive-exclude src/rust/target *
 
 recursive-exclude .github *
 

{cryptography-40.0.2/src/cryptography.egg-info → cryptography-41.0.1}/PKG-INFO

@@ -1,15 +1,14 @@
 Metadata-Version: 2.1
 Name: cryptography
-Version: 40.0.2
+Version: 41.0.1
 Summary: cryptography is a package which provides cryptographic recipes and primitives to Python developers.
-Home-page: https://github.com/pyca/cryptography
-Author: The Python Cryptographic Authority and individual contributors
-Author-email: cryptography-dev@python.org
-License: (Apache-2.0 OR BSD-3-Clause) AND PSF-2.0
-Project-URL: Documentation, https://cryptography.io/
-Project-URL: Source, https://github.com/pyca/cryptography/
-Project-URL: Issues, https://github.com/pyca/cryptography/issues
-Project-URL: Changelog, https://cryptography.io/en/latest/changelog/
+Author-email: The Python Cryptographic Authority and individual contributors <cryptography-dev@python.org>
+License: Apache-2.0 OR BSD-3-Clause
+Project-URL: homepage, https://github.com/pyca/cryptography
+Project-URL: documentation, https://cryptography.io/
+Project-URL: source, https://github.com/pyca/cryptography/
+Project-URL: issues, https://github.com/pyca/cryptography/issues
+Project-URL: changelog, https://cryptography.io/en/latest/changelog/
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: Apache Software License
@@ -23,7 +22,6 @@ Classifier: Operating System :: Microsoft :: Windows
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Programming Language :: Python :: 3.6
 Classifier: Programming Language :: Python :: 3.7
 Classifier: Programming Language :: Python :: 3.8
 Classifier: Programming Language :: Python :: 3.9
@@ -32,20 +30,19 @@ Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy
 Classifier: Topic :: Security :: Cryptography
-Requires-Python: >=3.6
+Requires-Python: >=3.7
 Description-Content-Type: text/x-rst
-Provides-Extra: tox
+Provides-Extra: ssh
+Provides-Extra: nox
 Provides-Extra: test
 Provides-Extra: test-randomorder
 Provides-Extra: docs
 Provides-Extra: docstest
 Provides-Extra: sdist
 Provides-Extra: pep8test
-Provides-Extra: ssh
 License-File: LICENSE
 License-File: LICENSE.APACHE
 License-File: LICENSE.BSD
-License-File: LICENSE.PSF
 
 pyca/cryptography
 =================
@@ -64,7 +61,7 @@ pyca/cryptography
 
 ``cryptography`` is a package which provides cryptographic recipes and
 primitives to Python developers. Our goal is for it to be your "cryptographic
-standard library". It supports Python 3.6+ and PyPy3 7.3.10+.
+standard library". It supports Python 3.7+ and PyPy3 7.3.10+.
 
 ``cryptography`` includes both high level recipes and low level interfaces to
 common cryptographic algorithms such as symmetric ciphers, message digests, and

{cryptography-40.0.2 → cryptography-41.0.1}/README.rst

@@ -15,7 +15,7 @@ pyca/cryptography
 
 ``cryptography`` is a package which provides cryptographic recipes and
 primitives to Python developers. Our goal is for it to be your "cryptographic
-standard library". It supports Python 3.6+ and PyPy3 7.3.10+.
+standard library". It supports Python 3.7+ and PyPy3 7.3.10+.
 
 ``cryptography`` includes both high level recipes and low level interfaces to
 common cryptographic algorithms such as symmetric ciphers, message digests, and

{cryptography-40.0.2 → cryptography-41.0.1}/docs/conf.py

@@ -72,7 +72,7 @@ master_doc = "index"
 
 # General information about the project.
 project = "Cryptography"
-copyright = "2013-2022, Individual Contributors"
+copyright = "2013-2023, Individual Contributors"
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
@@ -183,8 +183,7 @@ texinfo_documents = [
     ),
 ]
 
-# Example configuration for intersphinx: refer to the Python standard library.
-intersphinx_mapping = {"https://docs.python.org/3": None}
+intersphinx_mapping = {"python": ("https://docs.python.org/3", None)}
 
 epub_theme = "epub"
 
@@ -199,8 +198,6 @@ linkcheck_ignore = [
     r"https://info.isl.ntt.co.jp/crypt/eng/camellia/",
     # Inconsistent small DH params they seem incapable of fixing
     r"https://www.secg.org/sec1-v2.pdf",
-    # Cert is issued from an untrusted root
-    r"https://e-trust.gosuslugi.ru",
     # Incomplete cert chain
     r"https://www.oscca.gov.cn",
     # Cloudflare returns 403s for all non-browser requests

cryptography-41.0.1/docs/development/getting-started.rst

@@ -0,0 +1,66 @@
+Getting started
+===============
+
+Development dependencies
+------------------------
+
+Working on ``cryptography`` requires the installation of a small number of
+development dependencies in addition to the dependencies for
+:doc:`/installation`. These are handled by the use of ``nox``, which can be
+installed with ``pip``.
+
+.. code-block:: console
+
+    $ # Create a virtualenv and activate it
+    $ # Set up your cryptography build environment
+    $ pip install nox
+    $ # Specify your Python version here.
+    $ nox -e tests -p py310
+
+OpenSSL on macOS
+~~~~~~~~~~~~~~~~
+
+You must have installed `OpenSSL`_ (via `Homebrew`_ , `MacPorts`_, or a custom
+build) and must configure the build `as documented here`_ before calling
+``nox`` or else pip will fail to compile.
+
+Running tests
+-------------
+
+``cryptography`` unit tests are found in the ``tests/`` directory and are
+designed to be run using `pytest`_. ``nox`` automatically invokes ``pytest``:
+
+.. code-block:: console
+
+    $ nox -e tests -p py310
+    ...
+    62746 passed in 220.43 seconds
+
+
+Building documentation
+----------------------
+
+``cryptography`` documentation is stored in the ``docs/`` directory. It is
+written in `reStructured Text`_ and rendered using `Sphinx`_.
+
+Use `nox`_ to build the documentation. For example:
+
+.. code-block:: console
+
+    $ nox -e docs
+    ...
+    nox > Session docs was successful.
+
+The HTML documentation index can now be found at
+``docs/_build/html/index.html``.
+
+.. _`Homebrew`: https://brew.sh
+.. _`MacPorts`: https://www.macports.org
+.. _`OpenSSL`: https://www.openssl.org
+.. _`pytest`: https://pypi.org/project/pytest/
+.. _`nox`: https://pypi.org/project/nox/
+.. _`virtualenv`: https://pypi.org/project/virtualenv/
+.. _`pip`: https://pypi.org/project/pip/
+.. _`sphinx`: https://pypi.org/project/Sphinx/
+.. _`reStructured Text`: https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html
+.. _`as documented here`: https://docs.rs/openssl/latest/openssl/#automatic

{cryptography-40.0.2 → cryptography-41.0.1}/docs/development/submitting-patches.rst

@@ -21,8 +21,8 @@ Code
 When in doubt, refer to :pep:`8` for Python code. You can check if your code
 meets our automated requirements by formatting it with ``black`` and running
 ``ruff`` against it. If you've installed the development requirements this
-will automatically use our configuration. You can also run the ``tox`` job with
-``tox -e flake``.
+will automatically use our configuration. You can also run the ``nox`` job with
+``nox -e flake``.
 
 `Write comments as complete sentences.`_
 
@@ -95,7 +95,7 @@ Documentation
 -------------
 
 All features should be documented with prose in the ``docs`` section. To ensure
-it builds you can run ``tox -e docs``.
+it builds you can run ``nox -e docs``.
 
 Because of the inherent challenges in implementing correct cryptographic
 systems, we want to make our documentation point people in the right directions

{cryptography-40.0.2 → cryptography-41.0.1}/docs/development/test-vectors.rst

@@ -287,6 +287,10 @@ X.509
   a subject DN with a bit string type.
 * ``cryptography-scts-tbs-precert.der`` - The "to-be-signed" pre-certificate
   bytes from ``cryptography-scts.pem``, with the SCT list extension removed.
+* ``belgian-eid-invalid-visiblestring.pem`` - A certificate with UTF-8
+  bytes in a ``VisibleString`` type.
+* ``ee-pss-sha1-cert.pem`` - An RSA PSS certificate using a SHA1 signature and
+  SHA1 for MGF1 from the OpenSSL test suite.
 
 Custom X.509 Vectors
 ~~~~~~~~~~~~~~~~~~~~
@@ -478,11 +482,25 @@ Custom X.509 Vectors
   are longer than 2 characters.
 * ``rsa_pss_cert.pem`` - A self-signed certificate with an RSA PSS signature
   with ``asymmetric/PKCS8/rsa_pss_2048.pem`` as its key.
+* ``rsa_pss_cert_invalid_mgf.der`` - A self-signed certificate with an invalid
+  RSA PSS signature that has a non-MGF1 OID for its mask generation function in the
+  signature algorithm.
+* ``rsa_pss_cert_no_sig_params.der`` - A self-signed certificate with an invalid
+  RSA PSS signature algorithm that is missing signature parameters for PSS.
+* ``rsa_pss_cert_unsupported_mgf_hash.der`` - A self-signed certificate with an
+  unsupported MGF1 hash algorithm in the signature algorithm.
 * ``long-form-name-attribute.pem`` - A certificate with ``subject`` and ``issuer``
   names containing attributes whose value's tag is encoded in long-form.
 * ``mismatch_inner_outer_sig_algorithm.der`` - A leaf certificate derived from
   ``x509/cryptography.io.pem`` but modifying the ``tbs_cert.signature_algorithm``
   OID to not match the outer signature algorithm OID.
+* ``ms-certificate-template.pem`` - A certificate with a ``msCertificateTemplate``
+  extension.
+* ``rsa_pss_sha256_no_null.pem`` - A certificate with an RSA PSS signature
+  with no encoded ``NULL`` for the PSS hash algorithm parameters. This certificate
+  was generated by LibreSSL.
+* ``ecdsa_null_alg.pem`` - A certificate with an ECDSA signature with ``NULL``
+  algorithm parameters. This encoding is invalid, but was generated by Java 11.
 
 Custom X.509 Request Vectors
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -658,8 +676,10 @@ Custom X.509 OCSP Test Vectors
   extensions.
 * ``x509/ocsp/resp-unknown-extension.der`` - An OCSP response containing an
   extension with an unknown OID.
-* ``x509/ocsp/resp-unknown-hash-alg.der`` - AN OCSP response containing an
+* ``x509/ocsp/resp-unknown-hash-alg.der`` - An OCSP response containing an
   invalid hash algorithm OID.
+* ``x509/ocsp/req-acceptable-responses.der`` - An OCSP request containing an
+  acceptable responses extension.
 
 Custom PKCS12 Test Vectors
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -799,6 +819,10 @@ Custom PKCS7 Test Vectors
 Custom OpenSSH Test Vectors
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+* ``ed25519-aesgcm-psw.key`` and ``ed25519-aesgcm-psw.key.pub`` generated by
+  exporting an Ed25519 key from ``1password 8`` with the password "password".
+  This key is encrypted using the ``aes256-gcm@openssh.com`` algorithm.
+
 Generated by
 ``asymmetric/OpenSSH/gen.sh``
 using command-line tools from OpenSSH_7.6p1 package.
@@ -997,13 +1021,13 @@ header format (substituting the correct information):
 .. _`Specification repository`: https://github.com/fernet/spec
 .. _`errata`: https://www.rfc-editor.org/errata_search.php?rfc=6238
 .. _`OpenSSL example key`: https://github.com/openssl/openssl/blob/d02b48c63a58ea4367a0e905979f140b7d090f86/test/testrsa.pem
-.. _`GnuTLS key parsing tests`: https://gitlab.com/gnutls/gnutls/commit/f16ef39ef0303b02d7fa590a37820440c466ce8d
+.. _`GnuTLS key parsing tests`: https://gitlab.com/gnutls/gnutls/-/commit/f16ef39ef0303b02d7fa590a37820440c466ce8d
 .. _`enc-rsa-pkcs8.pem`: https://gitlab.com/gnutls/gnutls/blob/f8d943b38bf74eaaa11d396112daf43cb8aa82ae/tests/pkcs8-decode/encpkcs8.pem
 .. _`enc2-rsa-pkcs8.pem`: https://gitlab.com/gnutls/gnutls/blob/f8d943b38bf74eaaa11d396112daf43cb8aa82ae/tests/pkcs8-decode/enc2pkcs8.pem
 .. _`unenc-rsa-pkcs8.pem`: https://gitlab.com/gnutls/gnutls/blob/f8d943b38bf74eaaa11d396112daf43cb8aa82ae/tests/pkcs8-decode/unencpkcs8.pem
 .. _`pkcs12_s2k_pem.c`: https://gitlab.com/gnutls/gnutls/blob/f8d943b38bf74eaaa11d396112daf43cb8aa82ae/tests/pkcs12_s2k_pem.c
 .. _`Botan's ECC private keys`: https://github.com/randombit/botan/tree/4917f26a2b154e841cd27c1bcecdd41d2bdeb6ce/src/tests/data/ecc
-.. _`GnuTLS example keys`: https://gitlab.com/gnutls/gnutls/commit/ad2061deafdd7db78fd405f9d143b0a7c579da7b
+.. _`GnuTLS example keys`: https://gitlab.com/gnutls/gnutls/-/commit/ad2061deafdd7db78fd405f9d143b0a7c579da7b
 .. _`NESSIE IDEA vectors`: https://www.cosic.esat.kuleuven.be/nessie/testvectors/bc/idea/Idea-128-64.verified.test-vectors
 .. _`NESSIE`: https://en.wikipedia.org/wiki/NESSIE
 .. _`Ed25519 website`: https://ed25519.cr.yp.to/software.html

{cryptography-40.0.2 → cryptography-41.0.1}/docs/doing-a-release.rst

@@ -40,8 +40,7 @@ Bumping the version number
 The next step in doing a release is bumping the version number in the
 software.
 
-* Update the version number in ``src/cryptography/__about__.py``.
-* Update the version number in ``vectors/cryptography_vectors/__about__.py``.
+* Run ``python release.py bump-version {new_version}``
 * Set the release date in the :doc:`/changelog`.
 * Do a commit indicating this.
 * Send a pull request with this.
@@ -54,7 +53,7 @@ The commit that merged the version number bump is now the official release
 commit for this release. You will need to have ``gpg`` installed and a ``gpg``
 key in order to do a release. Once this has happened:
 
-* Run ``python release.py {version}``.
+* Run ``python release.py release {version}``.
 
 The release should now be available on PyPI and a tag should be available in
 the repository.
@@ -87,9 +86,8 @@ Post-release tasks
 * Close the `milestone`_ for the previous release on GitHub.
 * For major version releases, send a pull request to pyOpenSSL increasing the
   maximum ``cryptography`` version pin and perform a pyOpenSSL release.
-* Update the version number to the next major (e.g. ``0.5.dev1``) in
-  ``src/cryptography/__about__.py`` and
-  ``vectors/cryptography_vectors/__about__.py``.
+* Update the version number to the next major (e.g. ``0.5.dev1``) with
+  ``python release.py bump-version {new_version}``.
 * Add new :doc:`/changelog` entry with next version and note that it is under
   active development
 * Send a pull request with these items

{cryptography-40.0.2 → cryptography-41.0.1}/docs/faq.rst

@@ -1,6 +1,22 @@
 Frequently asked questions
 ==========================
 
+What issues can you help with in your issue tracker?
+----------------------------------------------------
+
+The primary purpose of our issue tracker is to enable us to identify and
+resolve bugs and feature requests in ``cryptography``, so any time a user
+files a bug, we start by asking: Is this a ``cryptography`` bug, or is it a
+bug somewhere else?
+
+That said, we do our best to help users to debug issues that are in their code
+or environments. Please note, however, that there's a limit to our ability to
+assist users in resolving problems that are specific to their environments,
+particularly when we have no way to reproduce the issue.
+
+Lastly, we're not able to provide support for general Python or Python
+packaging issues.
+
 .. _faq-howto-handle-deprecation-warning:
 
 I cannot suppress the deprecation warning that ``cryptography`` emits on import
@@ -102,15 +118,6 @@ If you have no other libraries using OpenSSL in your process, or they do not
 appear to be at fault, it's possible that this is a bug in ``cryptography``.
 Please file an `issue`_ with instructions on how to reproduce it.
 
-error: ``-Werror=sign-conversion``: No option ``-Wsign-conversion`` during installation
----------------------------------------------------------------------------------------
-
-The compiler you are using is too old and not supported by ``cryptography``.
-Please upgrade to a more recent version. If you are running OpenBSD 6.1 or
-earlier the default compiler is extremely old. Use ``pkg_add`` to install a
-newer ``gcc`` and then install ``cryptography`` using
-``CC=/path/to/newer/gcc pip install cryptography``.
-
 Installing cryptography with OpenSSL 0.9.8, 1.0.0, 1.0.1, 1.0.2, 1.1.0 fails
 ----------------------------------------------------------------------------
 
@@ -154,7 +161,7 @@ Why can't I import my PEM file?
 -------------------------------
 
 PEM is a format (defined by several RFCs, but originally :rfc:`1421`) for
-encoding keys, certificates and others cryptographic data into a regular form.
+encoding keys, certificates, and others cryptographic data into a regular form.
 The data is encoded as base64 and wrapped with a header and footer.
 
 If you are having trouble importing PEM files, make sure your file fits

{cryptography-40.0.2 → cryptography-41.0.1}/docs/hazmat/primitives/asymmetric/dh.rst

@@ -174,13 +174,6 @@ Group parameters
 
         :return bytes: Serialized parameters.
 
-.. class:: DHParametersWithSerialization
-
-    .. versionadded:: 1.7
-
-    Alias for :class:`DHParameters`.
-
-
 Key interfaces
 ~~~~~~~~~~~~~~
 
@@ -247,13 +240,6 @@ Key interfaces
         :return bytes: Serialized key.
 
 
-.. class:: DHPrivateKeyWithSerialization
-
-    .. versionadded:: 1.7
-
-    Alias for :class:`DHPrivateKey`.
-
-
 .. class:: DHPublicKey
 
     .. versionadded:: 1.7
@@ -293,13 +279,6 @@ Key interfaces
 
         :return bytes: Serialized key.
 
-.. class:: DHPublicKeyWithSerialization
-
-    .. versionadded:: 1.7
-
-    Alias for :class:`DHPublicKey`.
-
-
 Numbers
 ~~~~~~~
 

{cryptography-40.0.2 → cryptography-41.0.1}/docs/hazmat/primitives/asymmetric/dsa.rst

@@ -336,13 +336,6 @@ Key interfaces
         :return bytes: Serialized key.
 
 
-.. class:: DSAPrivateKeyWithSerialization
-
-    .. versionadded:: 0.8
-
-    Alias for :class:`DSAPrivateKey`.
-
-
 .. class:: DSAPublicKey
 
     .. versionadded:: 0.3
@@ -412,13 +405,6 @@ Key interfaces
             not validate.
 
 
-.. class:: DSAPublicKeyWithSerialization
-
-    .. versionadded:: 0.8
-
-    Alias for :class:`DSAPublicKey`.
-
-
 .. _`DSA`: https://en.wikipedia.org/wiki/Digital_Signature_Algorithm
 .. _`public-key`: https://en.wikipedia.org/wiki/Public-key_cryptography
 .. _`FIPS 186-4`: https://csrc.nist.gov/publications/detail/fips/186/4/final

{cryptography-40.0.2 → cryptography-41.0.1}/docs/hazmat/primitives/asymmetric/ec.rst

@@ -534,11 +534,7 @@ Key Interfaces
 
     .. versionadded:: 0.5
 
-    An elliptic curve private key for use with an algorithm such as `ECDSA`_ or
-    `EdDSA`_. An elliptic curve private key that is not an
-    :term:`opaque key` also implements
-    :class:`EllipticCurvePrivateKeyWithSerialization` to provide serialization
-    methods.
+    An elliptic curve private key for use with an algorithm such as `ECDSA`_.
 
     .. method:: exchange(algorithm, peer_public_key)
 
@@ -632,13 +628,6 @@ Key Interfaces
         :return bytes: Serialized key.
 
 
-.. class:: EllipticCurvePrivateKeyWithSerialization
-
-    .. versionadded:: 0.8
-
-    Alias for :class:`EllipticCurvePrivateKey`.
-
-
 .. class:: EllipticCurvePublicKey
 
     .. versionadded:: 0.5
@@ -734,13 +723,6 @@ Key Interfaces
             :class:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurve`.
 
 
-.. class:: EllipticCurvePublicKeyWithSerialization
-
-    .. versionadded:: 0.6
-
-    Alias for :class:`EllipticCurvePublicKey`.
-
-
 
 Serialization
 ~~~~~~~~~~~~~
@@ -937,7 +919,6 @@ Elliptic Curve Object Identifiers
 .. _`minimize the number of security concerns for elliptic-curve cryptography`: https://cr.yp.to/ecdh/curve25519-20060209.pdf
 .. _`SafeCurves`: https://safecurves.cr.yp.to/
 .. _`ECDSA`: https://en.wikipedia.org/wiki/ECDSA
-.. _`EdDSA`: https://en.wikipedia.org/wiki/EdDSA
 .. _`forward secrecy`: https://en.wikipedia.org/wiki/Forward_secrecy
 .. _`SEC 1 v2.0`: https://www.secg.org/sec1-v2.pdf
 .. _`bad cryptographic practice`: https://crypto.stackexchange.com/a/3313

{cryptography-40.0.2 → cryptography-41.0.1}/docs/hazmat/primitives/asymmetric/rsa.rst

@@ -642,13 +642,6 @@ Key interfaces
         :return bytes: Serialized key.
 
 
-.. class:: RSAPrivateKeyWithSerialization
-
-    .. versionadded:: 0.8
-
-    Alias for :class:`RSAPrivateKey`.
-
-
 .. class:: RSAPublicKey
 
     .. versionadded:: 0.2
@@ -783,13 +776,6 @@ Key interfaces
         :raises cryptography.exceptions.UnsupportedAlgorithm: If signature
             data recovery is not supported with the provided ``padding`` type.
 
-.. class:: RSAPublicKeyWithSerialization
-
-    .. versionadded:: 0.8
-
-    Alias for :class:`RSAPublicKey`.
-
-
 .. _`RSA`: https://en.wikipedia.org/wiki/RSA_(cryptosystem)
 .. _`public-key`: https://en.wikipedia.org/wiki/Public-key_cryptography
 .. _`specific mathematical properties`: https://en.wikipedia.org/wiki/RSA_(cryptosystem)#Key_generation