Use context specific for PKCS7 encrypted data encoding #7965
Conversation
This file contains 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
… it consistent with both old ASN code and openssl
SparkiDev
requested changes
Sep 12, 2024
ColtonWilley
changed the title
SparkiDev
approved these changes
Sep 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
While the current encoding for PKCS8 PBE is within specification, openssl will only parse the indefinite length form which the old ASN code used to generate before the move to the ASN template. Modify ASN template for PKCS8 PBE encoding to use indefinite length, making it consistent with both old ASN code and openssl expectations.
Fixes zd 18515