← Back to issue list

build(deps): bump cryptography from 41.0.7 to 42.0.2

View original Github issue

Metadata

Project
snapcraft
Number
#4591
Type
pull request
State
closed
Author
dependabot[bot]
Labels
—
Created
Updated
Closed

Current evaluation

Dependabot's cryptography 41.0.7→42.0.2 bump was closed unmerged as redundant: merged PR #4564 (commit ac421ab96) had already applied the same update, and Dependabot confirmed the dependency was current.

Resolution: closed superseded

Reason: PR #4564 "chore(deps): update dependency cryptography to v42 [security]" was merged first (commit ac421ab96), bringing cryptography to 42.0.2. Dependabot then commented on 2024-02-20 that cryptography was already up to date, and the PR was closed without merging.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Bumps [cryptography](https://github.com/pyca/cryptography) from 41.0.7 to 42.0.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst">cryptography's changelog</a>.</em></p> <blockquote> <p>42.0.2 - 2024-01-30</p> <pre><code> * Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.2.1. * Fixed an issue that prevented the use of Python buffer protocol objects in ``sign`` and ``verify`` methods on asymmetric keys. * Fixed an issue with incorrect keyword-argument naming with ``EllipticCurvePrivateKey`` :meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKey.exchange`, ``X25519PrivateKey`` :meth:`~cryptography.hazmat.primitives.asymmetric.x25519.X25519PrivateKey.exchange`, ``X448PrivateKey`` :meth:`~cryptography.hazmat.primitives.asymmetric.x448.X448PrivateKey.exchange`, and ``DHPrivateKey`` :meth:`~cryptography.hazmat.primitives.asymmetric.dh.DHPrivateKey.exchange`. <p>.. _v42-0-1:</p> <p>42.0.1 - 2024-01-24 </code></pre></p> <ul> <li>Fixed an issue with incorrect keyword-argument naming with <code>EllipticCurvePrivateKey</code> :meth:<code>~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKey.sign</code>.</li> <li>Resolved compatibility issue with loading certain RSA public keys in :func:<code>~cryptography.hazmat.primitives.serialization.load_pem_public_key</code>.</li> </ul> <p>.. _v42-0-0:</p> <p>42.0.0 - 2024-01-22</p> <pre><code> * **BACKWARDS INCOMPATIBLE:** Dropped support for LibreSSL &lt; 3.7. * **BACKWARDS INCOMPATIBLE:** Loading a PKCS7 with no content field using :func:`~cryptography.hazmat.primitives.serialization.pkcs7.load_pem_pkcs7_certificates` or :func:`~cryptography.hazmat.primitives.serialization.pkcs7.load_der_pkcs7_certificates` will now raise a ``ValueError`` rather than return an empty list. * Parsing SSH certificates no longer permits malformed critical options with values, as documented in the 41.0.2 release notes. * Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.2.0. * Updated the minimum supported Rust version (MSRV) to 1.63.0, from 1.56.0. * We now publish both ``py37`` and ``py39`` ``abi3`` wheels. This should resolve some errors relating to initializing a module multiple times per process. * Support :class:`~cryptography.hazmat.primitives.asymmetric.padding.PSS` for X.509 certificate signing requests and certificate revocation lists with the keyword-only argument ``rsa_padding`` on the ``sign`` methods for :class:`~cryptography.x509.CertificateSigningRequestBuilder` and :class:`~cryptography.x509.CertificateRevocationListBuilder`. * Added support for obtaining X.509 certificate signing request signature algorithm parameters (including PSS) via &lt;/tr&gt;&lt;/table&gt; </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pyca/cryptography/commit/2202123b50de1b8788f909a3e5afe350c56ad81e"><code>2202123</code></a> changelog and version bump 42.0.2 (<a href="https://redirect.github.com/pyca/cryptography/issues/10268">#10268</a>)</li> <li><a href="https://github.com/pyca/cryptography/commit/f7032bdd409838f67fc2b93343f897fb5f397d80"><code>f7032bd</code></a> bump openssl in CI (<a href="https://redirect.github.com/pyca/cryptography/issues/10298">#10298</a>) (<a href="https://redirect.github.com/pyca/cryptography/issues/10299">#10299</a>)</li> <li><a href="https://github.com/pyca/cryptography/commit/002e886f16d8857151c09b11dc86b35f2ac9aec3"><code>002e886</code></a> Fixes <a href="https://redirect.github.com/pyca/cryptography/issues/10294">#10294</a> -- correct accidental change to exchange kwarg (<a href="https://redirect.github.com/pyca/cryptography/issues/10295">#10295</a>) (<a href="https://redirect.github.com/pyca/cryptography/issues/10296">#10296</a>)</li> <li><a href="https://github.com/pyca/cryptography/commit/92fa9f2f606caea5d499c825e832be5bac6f0c23"><code>92fa9f2</code></a> support bytes-like consistently across our asym sign/verify APIs (<a href="https://redirect.github.com/pyca/cryptography/issues/10260">#10260</a>) (<a href="https://redirect.github.com/pyca/cryptography/issues/1">#1</a>...</li> <li><a href="https://github.com/pyca/cryptography/commit/6478f7e28be54b51931277235de01b249ceabd96"><code>6478f7e</code></a> explicitly support bytes-like for signature/data in RSA sign/verify (<a href="https://redirect.github.com/pyca/cryptography/issues/10259">#10259</a>) ...</li> <li><a href="https://github.com/pyca/cryptography/commit/4bb8596ae02d95bb054dbcf55e8771379dbe0c19"><code>4bb8596</code></a> fix the release script (<a href="https://redirect.github.com/pyca/cryptography/issues/10233">#10233</a>) (<a href="https://redirect.github.com/pyca/cryptography/issues/10254">#10254</a>)</li> <li><a href="https://github.com/pyca/cryptography/commit/337437dc2e62772bde4ad5544f4b1db9ee7572d9"><code>337437d</code></a> 42.0.1 bump (<a href="https://redirect.github.com/pyca/cryptography/issues/10252">#10252</a>)</li> <li><a href="https://github.com/pyca/cryptography/commit/56255de6b2d1a2d2e502b0275231ca81907f33f1"><code>56255de</code></a> allow SPKI RSA keys to be parsed even if they have an incorrect delimiter (<a href="https://redirect.github.com/pyca/cryptography/issues/1">#1</a>...</li> <li><a href="https://github.com/pyca/cryptography/commit/12f038b38af76e36efe8cef09597010c97647e8f"><code>12f038b</code></a> fixes <a href="https://redirect.github.com/pyca/cryptography/issues/10237">#10237</a> -- correct EC sign parameter name (<a href="https://redirect.github.com/pyca/cryptography/issues/10239">#10239</a>) (<a href="https://redirect.github.com/pyca/cryptography/issues/10240">#10240</a>)</li> <li><a href="https://github.com/pyca/cryptography/commit/4e64baf360a3a89bd92582f59344c12b5c0bd3fd"><code>4e64baf</code></a> 42.0.0 version bump (<a href="https://redirect.github.com/pyca/cryptography/issues/10232">#10232</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pyca/cryptography/compare/41.0.7...42.0.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cryptography&package-manager=pip&previous-version=41.0.7&new-version=42.0.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 <dependency name> 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/canonical/snapcraft/network/alerts). </details>

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed superseded Dependabot's cryptography 41.0.7→42.0.2 bump was closed unmerged as redundant: merged PR #4564 (commit ac421ab96) had already applied the same update, and Dependabot confirmed the dependency was current.
stealth/space-bunny-alpha — closed superseded Closed unmerged as redundant: #4564 had already applied the cryptography 41.0.7-to-42.0.2 update; Dependabot confirmed the dependency was current.
qwen/qwen3.6-35b-a3b — — Automated cryptography bump from 41.0.7 to 42.0.2 was closed as superseded. Dependabot confirmed the package is already up-to-date, making the update unnecessary.
qwen3.6-35b-a3b-mtp-q6 — — Closed as redundant. Dependabot proposed bumping cryptography to 42.0.2, but the dependency was already updated elsewhere, rendering the pull request unnecessary.

Update history

No update history recorded yet.

Related work

  • Superseded By: snapcraft#4564 (confidence 96%)

    Merged PR performing the identical cryptography 41.0.7 -> 42.0.2 update (commit ac421ab96), plus CVEs CVE-2023-50782/CVE-2024-0727.

Related issues

Issue Project State Summary Similarity
#4599 build(deps): bump cryptography from 42.0.2 to 42.0.4 snapcraft closed Dependabot bump of cryptography 42.0.2 -> 42.0.4 was closed unmerged; the same bump had already landed via Renovate PR #4598 (commit 7cfb60986), and Dependabot confirmed it was up-to-date.
95%
#4563 build(deps): bump cryptography from 41.0.7 to 42.0.0 snapcraft closed Dependabot's cryptography 41.0.7→42.0.0 bump PR was closed unmerged; maintainer @lengau closed it as "superseded by #4564", which merged cryptography 42.0.2 to fix CVE-2023-50782/CVE-2024-0727.
93%
#4280 build(deps): bump cryptography from 41.0.0 to 41.0.2 snapcraft closed Dependabot PR to bump cryptography 41.0.0→41.0.2 was closed unmerged; dependabot commented "Superseded by #4301", which upgraded directly to 41.0.3 and was merged as commit f38160c9d.
93%
#1395 build(deps): bump cryptography from 41.0.4 to 41.0.6 charmcraft closed Closed unmerged as redundant after commit d8a889db had already updated cryptography to v41.0.6; Dependabot confirmed the dependency was current.
93%
#4457 build(deps): bump cryptography from 41.0.4 to 41.0.6 snapcraft closed Closed unmerged as obsolete after cryptography was updated to 41.0.7; Dependabot said the 41.0.4→41.0.6 bump was no longer needed.
92%
#1163 build(deps): bump cryptography from 41.0.0 to 41.0.2 charmcraft closed Closed unmerged as redundant; cryptography 41.0.2 was applied by merged security PR #1164 in commit 6d9dd818.
89%
#1200 build(deps): bump cryptography from 41.0.2 to 41.0.3 charmcraft closed Dependabot's cryptography 41.0.2→41.0.3 bump was closed unmerged as redundant; the same update landed via security PR canonical/charmcraft#1201 (commit 31f7281c).
89%
#5251 build(deps): bump cryptography from 43.0.3 to 44.0.1 snapcraft closed Dependabot's cryptography 43.0.3→44.0.1 bump was closed unmerged: Dependabot repeatedly couldn't parse pyproject.toml, and mr-cal noted "Updated in #5290" before closing.
88%
#2645 build(deps): bump cryptography from 46.0.6 to 46.0.7 charmcraft closed Dependabot’s cryptography 46.0.7 bump was abandoned unmerged after two rebase requests; the bot stopped tracking that release.
86%
#2163 build(deps): update dependency cryptography to v44.0.1 [security] (main) - autoclosed charmcraft closed Renovate PR #2163 was autoclosed unmerged; the cryptography 44.0.1 update was instead merged through #2189 at commit bba6a32e.
85%