-
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
Unable to deal with ed25519 pk #81
Comments
I was able to export generated ed25519 key to pkcs8 using the ssh2 lib :
Hard to fond... It would be more convenient to have such function here. Thanks ! |
This was missing because the support for Ed25519 in PEM in With ECDSA, you should just be able to do |
True, and after re-rechecking, sometime there is differences 👀 The folliwng will print "test" for each pass, and will stop once pkcs8 are differents
Tested on node v12, v16, and v17, also tried on an other cpu. I make some stats, at the end I got ~50% of errors. On my side I send the pkcs8 to jose.importPKCS8 , and my tests pass 100% of time with the weird convertion I mentionned before. ??? ☁️ Thanks ! |
I'm desperatly trying to handle EdDSA / ed25519 private key in any library.
Most of them accept only PKCS8 format, while sshpk handle only PKCS1
Even node crypto can't import it :
Tried on node v12, v16, v17.
Thanks for help
The text was updated successfully, but these errors were encountered: