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 cryptography to 41.0.6 #920

Closed
wants to merge 1 commit into from

Conversation

pyup-bot
Copy link
Collaborator

This PR updates cryptography from 41.0.4 to 41.0.6.

Changelog

41.0.6

~~~~~~~~~~~~~~~~~~~

* Fixed a null-pointer-dereference and segfault that could occur when loading
certificates from a PKCS7 bundle.  Credit to **pkuzco** for reporting the
issue. **CVE-2023-49083**

.. _v41-0-5:

41.0.5

~~~~~~~~~~~~~~~~~~~

* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.1.4.
* Added a function to support an upcoming ``pyOpenSSL`` release.

.. _v41-0-4:
Links

Copy link

codecov bot commented Nov 27, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (df580ce) 90.47% compared to head (ce68fba) 90.47%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #920   +/-   ##
=======================================
  Coverage   90.47%   90.47%           
=======================================
  Files           6        6           
  Lines         294      294           
=======================================
  Hits          266      266           
  Misses         28       28           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pyup-bot
Copy link
Collaborator Author

Closing this in favor of #921

@pyup-bot pyup-bot closed this Nov 28, 2023
@hydrosquall hydrosquall deleted the pyup-update-cryptography-41.0.4-to-41.0.6 branch November 28, 2023 03:32
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.

1 participant