-
Notifications
You must be signed in to change notification settings - Fork 167
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
ED25519 support #443
Comments
Yes, OpenSSL handles Ed25519 separately in the EVP layer - Basic support for Ed25519 and X25519 is implemented by #370/#329 (please see the test code for Ed25519/X25519 example). It's currently only in master and not part of a release yet. |
When will it be part of the release? |
This is part of openssl v3.0.0. |
What am I doing wrong? It doesn't seem to be working somehow.
Ah, I see the problem:
|
I submitted #804 to allow requests to be signed using ED25519 |
openssl genpkey -algorithm ED25519 -out test.key
ruby -e "require 'openssl'; OpenSSL::PKey::EC.new('test.key')"
fails with "invalid curve name"The failure is somewhat expected as ED25519 keys aren't EC keys (they don't have a choice of curves) and this holds also for X25519, X448 and ED448.
This is preventing me from using an internal ED25519-based CA with Puppet.
Say I were interested in implementing them (or at least ED25519) would it be just appropriate to create more key types for each, analogous to the existing ones?
The text was updated successfully, but these errors were encountered: