Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency cryptography to v43 [SECURITY] #106

Open
wants to merge 1 commit into
base: 2/edge
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 4, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cryptography (changelog) ^42.0.8 -> ^43.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

GHSA-h4gh-qq45-vh27

pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 37.0.0-43.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20240903.txt.

If you are building cryptography source ("sdist") then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.


Release Notes

pyca/cryptography (cryptography)

v43.0.1

Compare Source

v43.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team September 4, 2024 00:30
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from 516454a to 1cd2c7f Compare September 12, 2024 13:15
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 2 times, most recently from 6f3a78e to cd64a67 Compare September 23, 2024 10:31
@renovate renovate bot changed the base branch from main to 2/edge September 24, 2024 22:54
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from a4acc8c to 9187a18 Compare October 18, 2024 19:26
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from bfd1a13 to 2965c3d Compare October 24, 2024 08:39
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 2 times, most recently from d395ea2 to 4953419 Compare November 12, 2024 18:12
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 3 times, most recently from 442f95d to 1b27d30 Compare November 28, 2024 18:38
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from 1b27d30 to 147b678 Compare December 5, 2024 12:49
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch 2 times, most recently from 2f18cfd to c2b0550 Compare December 18, 2024 17:38
@renovate renovate bot force-pushed the renovate/pypi-cryptography-vulnerability branch from c2b0550 to 09b73d5 Compare December 18, 2024 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants