PKCS#7 signing & verification - Certificate extension policies #13371
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the actual code changes of #12465 as requested by @alex. The test vectors are supplied in #13372.
It adds a new
pkcs7_x509_extension_policiesto thecryptography.hazmat.primitives.serialization.pkcs7module, which provides both CA and EE-Verification Policy for use e.g. with S/MIME.Please see #12465 for prior discussion and thanks to @nitneuqr to supply the code. This PR exists solely to comply with split PRs for test vectors and can happliy be closed If I misunderstood the task.