Switch to using SSLMate's PKCS#12 library #293
Merged
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
Contributor
Author
|
@jdtw May I request your review on this? |
Contributor
I'll take a look tomorrow! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Switch to using SSLMate's PKCS#12 library. The previous golang.org/x/crypto/pkcs12 library is frozen and not supported anymore. In particular, it doesn't support newer algorithms which are now seemingly the default in later versions of OpenSSL.
Here's an example of a PKCS#12 keystore (base64-encoded) generated with OpenSSL 3.0.2 which works with SSLMate's PKCS#12 library but does not work for me with the old Golang one:
(Had to base64-encode this because attaching binary files didn't seem to work).