try to support pkcs8 v2 format pem file for EdDSA#281
Merged
tomato42 merged 3 commits intotlsfuzzer:masterfrom Jan 4, 2022
Merged
try to support pkcs8 v2 format pem file for EdDSA#281tomato42 merged 3 commits intotlsfuzzer:masterfrom
tomato42 merged 3 commits intotlsfuzzer:masterfrom
Conversation
Contributor
Author
|
For ed25519 and ed448 in RFC5958, I think it should not raise error if something left after private key. |
Member
|
Change looks good but there are few nits reported by |
Contributor
Author
|
Of course
|
Contributor
Author
|
Furthemore, I want to know if you have rough plan to release version 0.18.0. Then I could use the function for EdDSA. |
Member
Member
|
black part of |
Contributor
Author
|
I think it should be fixed now. |
Member
|
Yup, looks good. Thanks! |
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
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.
Try to fix #280.
RFC5958 shows that pkcs8 v2 has the format:
There are maybe optional Attributes and Publickey after Privatekey. Thus it may not raise error when there are trailing data.