Adds export-p1 command #341
Merged
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
|
This PR is ready to merge. It also fixes the help text introduced in #340. |
TinCanTech
reviewed
Apr 25, 2022
TinCanTech
added
enhancement
initial-approval
and removed
conflicts
|
I fixed the conflicts. |
|
Yes, thanks. |
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.
Similar to #340 .
EasyRSA is useful to handle cert/key generation. But different software expects the key in different formats.
A trouble I have with EasyRSA is that the
build-cacommand generates a private key for the CA in PKCS#1 format. However, thegen-reqcommand generates keys in PKCS#8 format.This is confusing, since the "consumer" of the keys needs to realize the difference and process the keys differently.
This PR adds the
export-p1command that will convert keys to the PKCS#1 format.