dependabot[bot] opened a new pull request, #1991:
URL: https://github.com/apache/libcloud/pull/1991

   Bumps [cryptography](https://github.com/pyca/cryptography) from 41.0.6 to 
42.0.4.
   <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.4 - 2024-02-20</p>
   <pre><code>
   * Fixed a null-pointer-dereference and segfault that could occur when 
creating
     a PKCS#12 bundle. Credit to **Alexander-Programming** for reporting the
     issue. **CVE-2024-26130**
   * Fixed ASN.1 encoding for PKCS7/SMIME signed messages. The fields 
``SMIMECapabilities``
     and ``SignatureAlgorithmIdentifier`` should now be correctly encoded 
according to the
     definitions in :rfc:`2633` :rfc:`3370`.
   <p>.. _v42-0-3:</p>
   <p>42.0.3 - 2024-02-15
   </code></pre></p>
   <ul>
   <li>Fixed an initialization issue that caused key loading failures for some
   users.</li>
   </ul>
   <p>.. _v42-0-2:</p>
   <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>
   &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/fe18470f7d05f963e7267e34fdf985d81ea6ceea";><code>fe18470</code></a>
 Bump for 42.0.4 release (<a 
href="https://redirect.github.com/pyca/cryptography/issues/10445";>#10445</a>)</li>
   <li><a 
href="https://github.com/pyca/cryptography/commit/aaa2dd06ed470695de818405a982d4c459869803";><code>aaa2dd0</code></a>
 Fix ASN.1 issues in PKCS#7 and S/MIME signing (<a 
href="https://redirect.github.com/pyca/cryptography/issues/10373";>#10373</a>) 
(<a 
href="https://redirect.github.com/pyca/cryptography/issues/10442";>#10442</a>)</li>
   <li><a 
href="https://github.com/pyca/cryptography/commit/7a4d012991061974da5d9cb7614de65eac94f49b";><code>7a4d012</code></a>
 Fixes <a 
href="https://redirect.github.com/pyca/cryptography/issues/10422";>#10422</a> -- 
don't crash when a PKCS#12 key and cert don't match (<a 
href="https://redirect.github.com/pyca/cryptography/issues/10423";>#10423</a>) 
...</li>
   <li><a 
href="https://github.com/pyca/cryptography/commit/df314bb182bdfd661333969a94325e4680d785f6";><code>df314bb</code></a>
 backport actions m1 switch to 42.0.x (<a 
href="https://redirect.github.com/pyca/cryptography/issues/10415";>#10415</a>)</li>
   <li><a 
href="https://github.com/pyca/cryptography/commit/c49a7a5271178c6e8ef36fa1c499f62c63ec19b9";><code>c49a7a5</code></a>
 changelog and version bump for 42.0.3 (<a 
href="https://redirect.github.com/pyca/cryptography/issues/10396";>#10396</a>)</li>
   <li><a 
href="https://github.com/pyca/cryptography/commit/396bcf64c5be826ec00e7d7f45838c858c049cbc";><code>396bcf6</code></a>
 fix provider loading take two (<a 
href="https://redirect.github.com/pyca/cryptography/issues/10390";>#10390</a>) 
(<a 
href="https://redirect.github.com/pyca/cryptography/issues/10395";>#10395</a>)</li>
   <li><a 
href="https://github.com/pyca/cryptography/commit/0e0e46f5f73f477b8ee9682738c42129d5d60177";><code>0e0e46f</code></a>
 backport: initialize openssl's legacy provider in rust (<a 
href="https://redirect.github.com/pyca/cryptography/issues/10323";>#10323</a>) 
(<a 
href="https://redirect.github.com/pyca/cryptography/issues/10333";>#10333</a>)</li>
   <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>Additional commits viewable in <a 
href="https://github.com/pyca/cryptography/compare/41.0.6...42.0.4";>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.6&new-version=42.0.4)](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/apache/libcloud/network/alerts).
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@libcloud.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to