search

djaodjin / djaoapp

Web/API Gateway with user profiles, billing, and subscription-based access control
https://djaodjin.com/
Other
128 stars 33 forks source link

Bump cryptography from 2.2.2 to 41.0.3 #219

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps cryptography from 2.2.2 to 41.0.3.

Changelog

Sourced from cryptography's changelog.

41.0.3 - 2023-08-01


* Fixed performance regression loading DH public keys.
* Fixed a memory leak when using
  :class:`~cryptography.hazmat.primitives.ciphers.aead.ChaCha20Poly1305`.
* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.1.2.

.. _v41-0-2:


41.0.2 - 2023-07-10

  • Fixed bugs in creating and parsing SSH certificates where critical options with values were handled incorrectly. Certificates are now created correctly and parsing accepts correct values as well as the previously generated invalid forms with a warning. In the next release, support for parsing these invalid forms will be removed.

.. _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

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/djaodjin/djaoapp/network/alerts).
dependabot[bot] commented 1 year ago

Looks like cryptography is up-to-date now, so this is no longer needed.