-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node-sshpk#81 add support for ed25519 private keys in pkcs8 #83
Conversation
Please ACK that you've run "make test" including your new one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Asked about testing already, but otherwise seems good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one thing, then ready for merging.
der.startSequence(asn1.Ber.OctetString); | ||
var k = utils.mpNormalize(key.part.k.data); | ||
/* RFCs call for storing exactly 32 bytes, so strip any leading zeros */ | ||
while (k.length > 32 && k[0] == 0x00) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jsl is complaining that this should be ===
not ==
. If that's fixed, make check
will pass.
Excuse me, but is this project still alive? I saw that no commits have been made since January. Thanks |
Yes it's still alive. It hasn't been committed because it doesn't pass style checks. |
@arekinath Can you please fix the CI failure? |
Merged in #92. |
RFC8410 (PEM/X509 formats for Ed25519 and X25519) has been finalised for a while, this is the last piece of it that wasn't implemented in
sshpk
yet.Bumps version to 1.18.0 since this adds an API feature (support for converting Ed25519 keys to pkcs8 format).