-
Notifications
You must be signed in to change notification settings - Fork 2
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
Import/export in raw format of Ed25519 private keys #8
Comments
As was mentioned above, both ECDH and ECDSA signatures prevent from exporting private keys in raw format. This requirement could be extended to X25519, X448, ED25519, Ed448, if they are considered to be added in the standard. |
Am I missing something or is Node.js implementation of Ed25519 exclusive to Node.js? I have been trying to substitute Web Cryptography and/or polyfill code for |
It's also available on Cloudflare Workers/workerd. |
@vlovich FWIW This is what I wound up doing using Web Cryptography API. The same code works using Generate private and public keys: https://github.com/guest271314/webbundle/blob/main/generateWebCryptoKeys.js
Import private and public keys: https://github.com/guest271314/webbundle/blob/main/index.js#L11-L29
|
The spec is a little ambiguous with respect to how raw Ed25519 import/export should be handled. NodeJS allows raw import/export of Ed25519 private keys. I can't tell if this is an erratum in their implementation or an intentional difference from how ECDSA/ECDH work (no raw export for private keys). Similarly, the wording in the explainer document is awkwardly worded, at least to my reading.
Since raw is explicitly excluded as a X25519 thing, does this mean that the raw format isn't supported for Ed25519?
The text was updated successfully, but these errors were encountered: