-
Notifications
You must be signed in to change notification settings - Fork 89
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
Support cryptography 35.0.0 for the openssl_pkcs12 module #296
Support cryptography 35.0.0 for the openssl_pkcs12 module #296
Conversation
3046d89
to
ab26c4d
Compare
ab26c4d
to
aa2fcb7
Compare
ready_for_review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@Ajpantuso thanks for reviewing this! |
Backport to stable-1: 💚 backport PR created✅ Backport PR branch: Backported as #299 🤖 @patchback |
(cherry picked from commit d6c0d53)
…299) (cherry picked from commit d6c0d53) Co-authored-by: Felix Fontein <[email protected]>
SUMMARY
Follow-up to #294,
which right now includes #294. Will rebase once #294 is merged.Fixes #293.
Due to the friendly name being stored as the 'alias' of the X.509 cert, which isn't supported by cryptography's Rust code, we need to re-parse the PKCS#12 and extract the friendly name from the OpenSSL X.509 object directly. Once pyca/cryptography#6348 or something similar lands in cryptography we can get rid of this crutch...
ISSUE TYPE
COMPONENT NAME
openssl_pkcs12