Validate ECDSA and Ed25519 pub keys (elliptic curve) #24
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
Closed
|
Awesome work, thanks @mcclymont! |
|
Cheers @bensie. Are you planning to create a rubygems release with this? |
|
Yes thanks for the reminder, I'll take care of it tomorrow and drop another note here when it's pushed. |
|
v1.9.0 is pushed to RubyGems 🎉 |
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.
The validation is not very thorough, for ECDSA especially but I figured this is better than nothing.
This adds support for the class method valid_ssh_public_key? only, it doesn't allow you to generate elliptic curve keys or to instantiate an SSHKey with an elliptic curve private key.