Log message:
py-cryptography: update to 50.0.0.

50.0.0 - 2026-07-31
~~~~~~~~~~~~~~~~~~~

* **SECURITY ISSUE**:
  :func:`~cryptography.hazmat.primitives.serialization.pkcs7.pkcs7_decrypt_der`
  and its PEM and S/MIME variants no longer expose distinguishable errors or
  timing when unwrapping a ``RecipientInfo``'s ``encryptedKey``, which could
  act as a Bleichenbacher oracle for callers that decrypt untrusted messages.
  A random key is now substituted on failure, as described in :rfc:`3218`.
  Credit to **@X1AOxiang** for reporting the issue
* Deprecated Diffie-Hellman key exchange over finite fields (FFDH).
  Everything FFDH is deprecated, including the types in
  ``cryptography.hazmat.primitives.asymmetric.dh`` and loading FFDH keys or
  parameters with the key loading APIs. Users should migrate to a more
  modern key exchange algorithm.
* Added ``xof()`` class methods to
  :class:`~cryptography.hazmat.primitives.hashes.SHAKE128` and
  :class:`~cryptography.hazmat.primitives.hashes.SHAKE256` for constructing
  algorithm instances configured for use with
  :class:`~cryptography.hazmat.primitives.hashes.XOFHash`.
* The :mod:`X.509 verification <cryptography.x509.verification>` APIs are now
  considered stable and are subject to our API stability policy.
* Added the :doc:`/cobblestone` recipe, an implementation of the
  Cobblestone-128 and Cobblestone-256 instantiations of the `C2SP
  chunked-encryption specification
  <https://c2sp.org/chunked-encryption>`_ for streaming authenticated
  encryption of large messages.
* Parsing a Signed Certificate Timestamp list now rejects encodings that
  carry trailing bytes after the list or after an individual SCT, instead of
  silently ignoring them.
* Added support for using :class:`~cryptography.x509.Name` as a field type in
  the :doc:`/hazmat/asn1/index` module.
* Loading a public key or an EC private key now rejects DER where the
  ``subjectPublicKey`` (or EC ``publicKey``) ``BIT STRING`` declares a non-zero
  number of unused bits, instead of silently ignoring it.
* Parsing a CRL entry's ``InvalidityDate`` extension now rejects a
  ``GeneralizedTime`` that carries fractional seconds or another non-DER form,
  matching the strict encoding already required for every other X.509 time
  field.
* :func:`~cryptography.x509.ocsp.load_der_ocsp_request` and
  :func:`~cryptography.x509.ocsp.load_der_ocsp_response` now reject a request
  or response whose ``version`` field is not ``v1``, the only version defined
  by RFC 6960, matching the version validation already performed when loading
  certificates, CSRs and CRLs.
* :class:`~cryptography.hazmat.primitives.hashes.XOFHash` is now supported
  when building against AWS-LC.
* HMAC (and therefore PBKDF2-HMAC) with SHA-3 hashes is now supported when
  building against AWS-LC.
* Diffie-Hellman (:doc:`/hazmat/primitives/asymmetric/dh`) is now supported
  when building against AWS-LC.
* :func:`~cryptography.hazmat.primitives.serialization.load_der_public_key` and
  :func:`~cryptography.hazmat.primitives.serialization.load_pem_public_key` now
  reject Diffie-Hellman public keys whose modulus is smaller than 512 bits,
  matching the minimum already enforced when loading DH private keys and when
  constructing \ 
:class:`~cryptography.hazmat.primitives.asymmetric.dh.DHParameterNumbers`.
* Added
  :class:`~cryptography.hazmat.primitives.asymmetric.mldsa.MLDSAMuHasher` for
  incrementally computing the ML-DSA ``mu`` (message representative) used by
  the external-mu signing and verification APIs.
* The builtin :class:`~cryptography.hazmat.primitives.hashes.HashAlgorithm`
  classes and the classes in
  :mod:`~cryptography.hazmat.primitives.asymmetric.padding` can now be
  compared with ``==``.
* :class:`~cryptography.x509.CertificateBuilder` now supports creating unsigned
  certificates (:rfc:`9925`) with the ``create_unsigned`` method.
* The :mod:`X.509 verification <cryptography.x509.verification>` APIs now
  permit ML-DSA-44, ML-DSA-65, and ML-DSA-87 (:rfc:`9881`) public keys and
  signatures by default.

Log message:
py-cryptography: update to 49.0.0.

49.0.0 - 2026-06-12

    BACKWARDS INCOMPATIBLE: Support for x86_64 macOS has been removed. We now \ 
only publish arm64 wheels for macOS.
    BACKWARDS INCOMPATIBLE: Support for 32-bit Windows has been removed. Users \ 
should move to a 64-bit Python installation.
    BACKWARDS INCOMPATIBLE: Removed the deprecated PUBLIC_KEY_TYPES, \ 
PRIVATE_KEY_TYPES, CERTIFICATE_PRIVATE_KEY_TYPES, \ 
CERTIFICATE_ISSUER_PUBLIC_KEY_TYPES, and CERTIFICATE_PUBLIC_KEY_TYPES type \ 
aliases. Use PublicKeyTypes, PrivateKeyTypes, CertificateIssuerPrivateKeyTypes, \ 
CertificateIssuerPublicKeyTypes, and CertificatePublicKeyTypes instead. These \ 
were deprecated in version 40.0.
    BACKWARDS INCOMPATIBLE: \ 
:class:`~cryptography.hazmat.primitives.ciphers.algorithms.ChaCha20` now treats \ 
the first 4 bytes of the nonce as a 32-bit little-endian block counter (as \ 
defined in RFC 7539) and tracks the number of bytes processed. Attempting to \ 
encrypt or decrypt more data than the counter allows before it would overflow \ 
now raises a :class:`ValueError` rather than silently diverging from RFC 7539. \ 
Setting the counter portion of the nonce to zero allows encrypting up to 256 GiB \ 
with a given nonce.
    BACKWARDS INCOMPATIBLE: Loading an X.509 certificate whose ECDSA or DSA \ 
signature AlgorithmIdentifier contains encoded NULL parameters now raises a \ 
:class:`ValueError`. Such certificates are invalid, but older versions of Java \ 
emitted them; previously they loaded with a deprecation warning.
    Fixed cross-compilation of the CFFI bindings when PYO3_CROSS_LIB_DIR is set. \ 
The build now derives the Python include directory from PYO3_CROSS_LIB_DIR \ 
instead of querying the host interpreter, which previously caused the build to \ 
fail during cross-compilations for embedded systems, on hosts which have \ 
same-version Python development headers installed as the target Python.
    Added support for signing and verifying X.509 certificates, certificate \ 
signing requests, and certificate revocation lists with \ 
:doc:`/hazmat/primitives/asymmetric/mldsa` keys, as well as loading certificates \ 
that contain ML-DSA public keys.
    Added :meth:`~cryptography.hazmat.primitives.hpke.KEM.enc_length` to \ 
:class:`~cryptography.hazmat.primitives.hpke.KEM` so callers can split the \ 
encapsulated key from the ciphertext returned by \ 
:meth:`~cryptography.hazmat.primitives.hpke.Suite.encrypt`.
    :meth:`~cryptography.x509.verification.ExtensionPolicy.require_present`, \ 
:meth:`~cryptography.x509.verification.ExtensionPolicy.may_be_present`, and \ 
:meth:`~cryptography.x509.verification.ExtensionPolicy.require_not_present` now \ 
accept any extension type. Previously only a fixed set of extension types was \ 
supported, which made it impossible to account for otherwise unrecognized \ 
critical extensions during path validation.
    Added support for using :class:`~cryptography.x509.Certificate`, \ 
:class:`~cryptography.x509.CertificateSigningRequest`, and \ 
:class:`~cryptography.x509.CertificateRevocationList` as field types in \ 
:doc:`/hazmat/asn1/index` structures.
    Added :func:`~cryptography.hazmat.asn1.value_set`, a class decorator that \ 
registers an :class:`enum.Enum` subclass as an ASN.1 value set: members are \ 
encoded as their underlying value, and decoding fails if the decoded value does \ 
not match one of the declared members.
    Added :meth:`~cryptography.x509.Name.from_bytes` for parsing a \ 
:class:`~cryptography.x509.Name` from DER bytes, the inverse of \ 
:meth:`~cryptography.x509.Name.public_bytes`.
    Added the rsa_padding keyword-only parameter to \ 
:meth:`~cryptography.x509.CertificateBuilder.public_key`. Passing the \ 
:class:`~cryptography.hazmat.primitives.asymmetric.padding.PSS` class (not an \ 
instance) encodes an RSA subject public key in the certificate's \ 
subjectPublicKeyInfo with the id-RSASSA-PSS OID and no parameters.
    Added external mu (message representative) support to \ 
:doc:`/hazmat/primitives/asymmetric/mldsa` via the sign_mu and verify_mu \ 
methods, which sign and verify a precomputed 64-byte mu as defined in FIPS 204.

Log message:
py-cryptography py-cryptography_vectors: updated to 48.0.1

48.0.1
Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 4.0.1.

Log message:
py-cryptography reqires openssl3, make it so

PR 60255 by riastradh

Log message:
py-cryptography py-cryptography_vectors: updated to 48.0.0

48.0.0 - 2026-05-04

* **BACKWARDS INCOMPATIBLE:** Support for Python 3.8 has been removed.
  ``cryptography`` now requires Python 3.9 or later.
* **BACKWARDS INCOMPATIBLE:** Loading an X.509 CRL whose inner
  ``TBSCertList.signature`` algorithm does not match the outer
  ``signatureAlgorithm`` now raises ``ValueError``. Previously, such CRLs
  were parsed successfully and only rejected during signature validation.
* Added support for :doc:`/hazmat/primitives/asymmetric/mlkem` and
  :doc:`/hazmat/primitives/asymmetric/mldsa` when using OpenSSL 3.5.0 or
  later, in addition to the existing AWS-LC and BoringSSL support. This means
  post-quantum algorithms are now available to users of our wheels.

  * **Note:** Going forward, we do not guarantee that all functionality
    in ``cryptography`` will be available when building against
    OpenSSL. See :doc:`/statements/state-of-openssl` for more information.

Log message:
py-cryptography py-cryptography_vectors: updated to 47.0.0

47.0.0 - 2026-04-24

Support for Python 3.8 is deprecated and will be removed in the next \ 
cryptography release.
BACKWARDS INCOMPATIBLE: Support for binary elliptic curves (SECT* classes) has \ 
been removed. These curves are rarely used and have additional security \ 
considerations that make them undesirable.
BACKWARDS INCOMPATIBLE: Support for OpenSSL 1.1.x has been removed. OpenSSL \ 
3.0.0 or later is now required. LibreSSL, BoringSSL, and AWS-LC continue to be \ 
supported.
BACKWARDS INCOMPATIBLE: Dropped support for LibreSSL < 4.1.
BACKWARDS INCOMPATIBLE: Loading keys with unsupported algorithms or keys with \ 
unsupported explicit curve encodings now raises \ 
:class:`~cryptography.exceptions.UnsupportedAlgorithm` instead of ValueError. \ 
This change affects \ 
:func:`~cryptography.hazmat.primitives.serialization.load_pem_private_key`, \ 
:func:`~cryptography.hazmat.primitives.serialization.load_der_private_key`, \ 
:func:`~cryptography.hazmat.primitives.serialization.load_pem_public_key`, \ 
:func:`~cryptography.hazmat.primitives.serialization.load_der_public_key`, and \ 
:meth:`~cryptography.x509.Certificate.public_key` when called on certificates \ 
with unsupported public key algorithms.
BACKWARDS INCOMPATIBLE: When parsing elliptic curve private keys, we now reject \ 
keys that incorrectly encode a private key of the wrong length because such keys \ 
are impossible to process in a constant-time manner. We do not believe keys with \ 
this problem are in wide use, however we may revert this change based on the \ 
feedback we receive.
Deprecated passing 64-bit (8-byte) and 128-bit (16-byte) keys to \ 
:class:`~cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES`. In a future \ 
release, only 192-bit (24-byte) keys will be accepted. Users should expand \ 
shorter keys themselves (e.g., for single DES: key + key + key, for two-key: key \ 
+ key[:8]).
Updated the minimum supported Rust version (MSRV) to 1.83.0, from 1.74.0.
Support for x86_64 macOS (including publishing wheels) is deprecated and will be \ 
removed in the next release. We will switch to publishing an arm64 only wheel \ 
for macOS.
Support for 32-bit Windows (including publishing wheels) is deprecated and will \ 
be removed in the next release. Users should move to a 64-bit Python \ 
installation.
public_bytes and private_bytes methods on keys now raise TypeError (instead of \ 
ValueError) if an invalid encoding is provided for the given format.
Moved :class:`~cryptography.hazmat.decrepit.ciphers.modes.CFB`, \ 
:class:`~cryptography.hazmat.decrepit.ciphers.modes.OFB`, and \ 
:class:`~cryptography.hazmat.decrepit.ciphers.modes.CFB8` into \ 
:doc:`/hazmat/decrepit/index` and deprecated them in the modes module. They will \ 
be removed from the modes module in 49.0.0.
Moved :class:`~cryptography.hazmat.primitives.ciphers.algorithms.Camellia` into \ 
:doc:`/hazmat/decrepit/index` and deprecated it in the cipher module. It will be \ 
removed from the cipher module in 49.0.0.
Added :meth:`~cryptography.hazmat.primitives.kdf.hkdf.HKDF.extract` to \ 
:class:`~cryptography.hazmat.primitives.kdf.hkdf.HKDF`. The previous private \ 
implementation will be removed in 49.0.0.
Added support for loading elliptic curve keys that contain explicit encodings of \ 
the curves secp256r1, secp384r1, and secp521r1.
Added support for :class:`~cryptography.hazmat.primitives.kdf.argon2.Argon2d` \ 
and :class:`~cryptography.hazmat.primitives.kdf.argon2.Argon2i` when using \ 
OpenSSL 3.2.0+.
Added derive_into methods to \ 
:class:`~cryptography.hazmat.primitives.kdf.hkdf.HKDF`, \ 
:class:`~cryptography.hazmat.primitives.kdf.hkdf.HKDFExpand`, \ 
:class:`~cryptography.hazmat.primitives.kdf.concatkdf.ConcatKDFHash`, \ 
:class:`~cryptography.hazmat.primitives.kdf.concatkdf.ConcatKDFHMAC`, \ 
:class:`~cryptography.hazmat.primitives.kdf.argon2.Argon2id`, \ 
:class:`~cryptography.hazmat.primitives.kdf.pbkdf2.PBKDF2HMAC`, \ 
:class:`~cryptography.hazmat.primitives.kdf.kbkdf.KBKDFHMAC`, \ 
:class:`~cryptography.hazmat.primitives.kdf.kbkdf.KBKDFCMAC`, \ 
:class:`~cryptography.hazmat.primitives.kdf.scrypt.Scrypt`, and \ 
:class:`~cryptography.hazmat.primitives.kdf.x963kdf.X963KDF` to allow deriving \ 
keys directly into pre-allocated buffers.
Added encrypt_into and decrypt_into methods to \ 
:class:`~cryptography.hazmat.primitives.ciphers.aead.AESCCM`, \ 
:class:`~cryptography.hazmat.primitives.ciphers.aead.AESGCM`, \ 
:class:`~cryptography.hazmat.primitives.ciphers.aead.AESGCMSIV`, \ 
:class:`~cryptography.hazmat.primitives.ciphers.aead.AESOCB3`, \ 
:class:`~cryptography.hazmat.primitives.ciphers.aead.AESSIV`, and \ 
:class:`~cryptography.hazmat.primitives.ciphers.aead.ChaCha20Poly1305` to allow \ 
encrypting directly into a pre-allocated buffer.
Added support for PKCS1v15 signing without DigestInfo using \ 
:class:`~cryptography.hazmat.primitives.asymmetric.utils.NoDigestInfo`.
Added :meth:`~cryptography.hazmat.primitives.hashes.Hash.hash`, a one-shot \ 
method for computing hashes.
Added :doc:`/hazmat/primitives/hpke` support implementing RFC 9180 for hybrid \ 
authenticated encryption.
Added new :doc:`/hazmat/primitives/asymmetric/mlkem` module with support for \ 
ML-KEM key encapsulation with AWS-LC and BoringSSL.
Note: Post-quantum algorithm support requires AWS-LC or BoringSSL. As we ship \ 
our wheels with OpenSSL, most users will not have access to these APIs yet. See \ 
:doc:`/statements/state-of-openssl` for more information on OpenSSL support.
Added new :doc:`/hazmat/primitives/asymmetric/mldsa` module with support for \ 
ML-DSA signing and verification with AWS-LC and BoringSSL.
Note: Post-quantum algorithm support requires AWS-LC or BoringSSL. As we ship \ 
our wheels with OpenSSL, most users will not have access to these APIs yet. See \ 
:doc:`/statements/state-of-openssl` for more information on OpenSSL support.
Added new :doc:`/hazmat/asn1/index` module with support for declaratively \ 
defining custom ASN.1 types and encoding/decoding them.
Fixed compilation when using LibreSSL 4.3.0 and OpenSSL 4.0.0.
Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 4.0.0.

Log message:
py-cryptography: update to 46.0.7.

46.0.7 - 2026-01-27
~~~~~~~~~~~~~~~~~~~

* **SECURITY ISSUE**: Fixed an issue where non-contiguous buffers could be
  passed to APIs that accept Python buffers, which could lead to buffer
  overflow. **CVE-2026-39892**
* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.5.6.

Log message:
py-cryptography py-cryptography_vectors: updated to 46.0.6

46.0.6 - 2026-03-25

* **SECURITY ISSUE**: Fixed a bug where name constraints were not applied
  to peer names during verification when the leaf certificate contains a
  wildcard DNS SAN. Ordinary X.509 topologies are not affected by this bug,
  including those used by the Web PKI. Credit to **Oleh Konko (1seal)** for
  reporting the issue. **CVE-2026-34073**