More PKCS8 v2 encryption options #5656
Closed
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
Fixes: pyca#4272 Signed-off-by: Christian Heimes <cheimes@redhat.com>
|
LibreSSL doesn't have |
|
Is this something you plan to revisit @tiran? |
Yes, I'll pick up the PR in a couple of weeks. For now I'm focusing on Python 3.10 and OpenSSL 3.0.0 work. 3.10 feature freeze is in a couple of weeks. |
|
Closing for the same reason we closed #6569. If you'd like to discuss approach and finish this out feel free to reopen. |
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.
Very rough PoC for enhanced KeySerializationEncryption. @bhoefer2015 has asked me to look into the matter. The code in
_private_key_pkcs8is based on OpenSSL'sapps/pkcs8.c. I haven't figured out a good user-facing API yet.Fixes: #4272
Signed-off-by: Christian Heimes cheimes@redhat.com