Skip to content

Bump cryptography from 3.2 to 39.0.1 - #749

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/cryptography-39.0.1
Open

Bump cryptography from 3.2 to 39.0.1#749
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/cryptography-39.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Feb 8, 2023

Copy link
Copy Markdown

Bumps cryptography from 3.2 to 39.0.1.

Changelog

Sourced from cryptography's changelog.

39.0.1 - 2023-02-07


* **SECURITY ISSUE** - Fixed a bug where ``Cipher.update_into`` accepted Python
  buffer protocol objects, but allowed immutable buffers. **CVE-2023-23931**
* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.0.8.

.. _v39-0-0:

39.0.0 - 2023-01-01

  • BACKWARDS INCOMPATIBLE: Support for OpenSSL 1.1.0 has been removed. Users on older version of OpenSSL will need to upgrade.
  • BACKWARDS INCOMPATIBLE: Dropped support for LibreSSL < 3.5. The new minimum LibreSSL version is 3.5.0. Going forward our policy is to support versions of LibreSSL that are available in versions of OpenBSD that are still receiving security support.
  • BACKWARDS INCOMPATIBLE: Removed the encode_point and from_encoded_point methods on :class:~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicNumbers, which had been deprecated for several years. :meth:~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey.public_bytes and :meth:~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey.from_encoded_point should be used instead.
  • BACKWARDS INCOMPATIBLE: Support for using MD5 or SHA1 in :class:~cryptography.x509.CertificateBuilder, other X.509 builders, and PKCS7 has been removed.
  • BACKWARDS INCOMPATIBLE: Dropped support for macOS 10.10 and 10.11, macOS users must upgrade to 10.12 or newer.
  • ANNOUNCEMENT: The next version of cryptography (40.0) will change the way we link OpenSSL. This will only impact users who build cryptography from source (i.e., not from a wheel), and specify their own version of OpenSSL. For those users, the CFLAGS, LDFLAGS, INCLUDE, LIB, and CRYPTOGRAPHY_SUPPRESS_LINK_FLAGS environment variables will no longer be respected. Instead, users will need to configure their builds as documented here_.
  • Added support for :ref:disabling the legacy provider in OpenSSL 3.0.x<legacy-provider>.
  • Added support for disabling RSA key validation checks when loading RSA keys via :func:~cryptography.hazmat.primitives.serialization.load_pem_private_key, :func:~cryptography.hazmat.primitives.serialization.load_der_private_key, and :meth:~cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateNumbers.private_key. This speeds up key loading but is :term:unsafe if you are loading potentially attacker supplied keys.
  • Significantly improved performance for :class:~cryptography.hazmat.primitives.ciphers.aead.ChaCha20Poly1305

... (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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [cryptography](https://github.com/pyca/cryptography) from 3.2 to 39.0.1.
- [Release notes](https://github.com/pyca/cryptography/releases)
- [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst)
- [Commits](pyca/cryptography@3.2...39.0.1)

---
updated-dependencies:
- dependency-name: cryptography
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Feb 8, 2023
DAB-LABS added a commit to DAB-LABS/python-broadlink that referenced this pull request Sep 5, 2026
* Add support for Broadlink RM Max (0xAF8B)

Place in the rmpro class which uses <I framing for IR learn/send
commands, matching the device's actual protocol. The rm4pro class
uses <HI framing which causes "device is locked" errors on this
hardware.

Co-authored-by: Cursor <cursoragent@cursor.com>

* Update __init__.py

* Update remote.py

* Add an OEM device code for RM mini 3

* support RM mini 3 cmcc version

support RM mini 3 cmcc version

* Added support for another type of LB26 R1

* Update __init__.py

add 0x7d15 SP mini 3-AL

* Add support for LEDVANCE SMART+ WIFI CEILING TW 24W (0x6498)

* Refactor tick parameter to use constant value

* Add tests for TICK constant in remote module

Add unit tests for the TICK constant in remote module to ensure accuracy against protocol.md examples and validate behavior with real hardware.

* Round pulses to the nearest tick, add issue-reported device IDs, update tests and changelog

Follow-ups to the carried-over commits:

- pulses_to_data rounds instead of truncating, so a duration that is
  0.9 of a tick no longer becomes zero ticks.
- TICK gets a docstring explaining the 32768 Hz timebase and the history
  of the 32.84 value; the import block is sorted for ruff.
- 0x4EDA MP1-1K3S2U (mjg59#816) and 0xA57A SP4 (mjg59#758) added from issues, by
  family; 0x7D15 and 0x27C8 entries tidied into hex order and house style.
- cryptography floor raised to 43, the first release with 3.13 wheels
  (supersedes mjg59#749).
- tests/test_helpers.py re-pinned to the new tick and rounding; the old
  32.84 pins are gone.
- README device list and CHANGELOG updated.

---------

Co-authored-by: Alexey Masolov <amasolov@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Anil Daoud <anil.daoud@protonmail.com>
Co-authored-by: Bartłomiej Nogaś <bart.nogas@gmail.com>
Co-authored-by: shuxin <shuxin@users.noreply.github.com>
Co-authored-by: techitapart <70172453+techitapart@users.noreply.github.com>
Co-authored-by: bbcbbk <44605459+bbcbbk@users.noreply.github.com>
Co-authored-by: Felipe Martins Diel <felipe-diel@hotmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants