-
Notifications
You must be signed in to change notification settings - Fork 204
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
Add support for 25519 and 448 #89
Comments
FYI: There's a proposal to bring Curve25519 to WebCrypto (see also tQsW/webcrypto-curve25519#6). Although I guess we'd also need |
Support for both curves just landed on Node 15.8: nodejs/node@53a0bdff47 |
@gnarea PRs welcomed /cc @microshine |
I like the idea to support those curves |
I'll try to have a go in the coming weeks. Presumably we'll have to change https://github.com/PeculiarVentures/webcrypto too, and make sure that when other engines (e.g., the browser-based one) use of these algorithms a meaningful error is thrown (like "Ed25519 is not supported by this engine"). |
@gnarea The latest version of |
@gnarea For which operation do you need those curves (eg CSR/cert generation, chain validation, etc)? |
Awesome! 👏 👏 I only need to do these things with Ed25519/Ed448:
|
I'm going to support those mechanisms in PKIjs allows supporting new mechanism by extending |
That's amazing! We're in a code freeze right now because we're getting ready to launch, but I'll try it as soon as I can afterwards. |
@gnarea I added an example with an updated liner for trying |
Thanks for the example @microshine! Seems pretty straightforward which is awesome. |
Can you make it possible to encrypt/decrypt with x25519? This is possible with node's webcrypto experiment with 25519 curves. |
@CMCDragonkai, that'd require implementing RFC 8418, which I believe would be different from the OP. That's something I've wanted to contribute for a while but haven't had the chance so far. Maybe if you have the time and the Peculiar Ventures team like the idea of supporting RFC 8418, you could discuss how you'd do implement it and propose a PR. See also: #254 |
https://datatracker.ietf.org/doc/draft-ietf-curdle-pkix/
The text was updated successfully, but these errors were encountered: