python-cryptography

Edit Package python-cryptography
No description set
Refresh
Refresh
Source Files
Filename Size Changed
_multibuild 0000000053 53 Bytes
_service 0000000299 299 Bytes
cargo_config 0000000100 100 Bytes
cryptography-38.0.1.tar.gz 0000599412 585 KB
python-cryptography.changes 0000062905 61.4 KB
python-cryptography.keyring 0000001847 1.8 KB
python-cryptography.spec 0000003987 3.89 KB
remove_python_3_6_deprecation_warning.patch 0000000703 703 Bytes
skip_openssl_memleak_test.patch 0000000794 794 Bytes
vendor.tar.zst 0007636953 7.28 MB
Revision 67 (latest revision is 90)
Dominique Leuenberger's avatar Dominique Leuenberger (dimstar_suse) accepted request 1007100 from Dirk Mueller's avatar Dirk Mueller (dirkmueller) (revision 67)
- update to 38.0.1:
  * Fixed parsing TLVs in ASN.1 with length greater than 65535 bytes (typically
    seen in large CRLs).
  * Final deprecation of OpenSSL 1.1.0. The next release of ``cryptography``
    will drop support.
  * We no longer ship ``manylinux2010`` wheels. Users should upgrade to the
    latest ``pip`` to ensure this doesn't cause issues downloading wheels on
    their platform. We now ship ``manylinux_2_28`` wheels for users on new
    enough platforms.
  * Updated the minimum supported Rust version (MSRV) to 1.48.0, from 1.41.0.
    Users with the latest ``pip`` will typically get a wheel and not need Rust
    installed, but check :doc:`/installation` for documentation on installing a
    newer ``rustc`` if required.
  * :meth:`~cryptography.fernet.Fernet.decrypt` and related methods now accept
    both ``str`` and ``bytes`` tokens.
  * Parsing ``CertificateSigningRequest`` restores the behavior of enforcing
    that the ``Extension`` ``critical`` field must be correctly encoded DER. See
    `the issue <https://github.com/pyca/cryptography/issues/6368>`_ for complete
    details.
  * Added two new OpenSSL functions to the bindings to support an upcoming
    ``pyOpenSSL`` release.
  * When parsing :class:`~cryptography.x509.CertificateRevocationList` and
    :class:`~cryptography.x509.CertificateSigningRequest` values, it is now
    enforced that the ``version`` value in the input must be valid according to
    the rules of :rfc:`2986` and :rfc:`5280`.
  * Using MD5 or SHA1 in :class:`~cryptography.x509.CertificateBuilder` and
    other X.509 builders is deprecated and support will be removed in the next
    version.
  * Added additional APIs to
    :class:`~cryptography.x509.certificate_transparency.SignedCertificateTimestamp`, including
Comments 0
openSUSE Build Service is sponsored by