support for Curve25519 in WebCrypto.

Question

support for Curve25519 in WebCrypto.

dontcallmedom opened this issue 5 years ago · 5 comments

A proposal to add Curve25519 was brought to the TAG:
https://github.com/tQsW/webcrypto-curve25519/blob/master/explainer.md

I thought it would make sense to log it here

Answer 1 · 2020-02-03T15:21:53.000Z

Another important curve specified already in TLS standard https://tools.ietf.org/html/rfc8446 and CFRG https://tools.ietf.org/html/rfc7748 is curve448. I think we need to add it to the web crypto. Here is my quick post in wicg https://discourse.wicg.io/t/proposal-add-curve-25519-and-cruve-448-to-the-web-cryptography-api/4153

Answer 2 · 2021-01-29T12:44:07.000Z

Dom, if any members of the TAG or others would like to see this proposal get some consideration, somebody needs to do the work of engaging with browser-engine implementors about it here.

Answer 3 · 2021-01-29T13:09:33.000Z

@sideshowbarker I belive @tQsW works for an implementer (Google) and the proposal had received contributions from @martinthomson who works for another (Mozilla); paging @wseltzer who was involved in some related discussions I believe

Answer 4 · 2021-05-07T17:39:41.000Z

I wanted to highlight an ambiguity I noticed (tQsW/webcrypto-curve25519#8) when I was reviewing NodeJS's implementation (nodejs/node#36879) which seems to allow import/export of private keys in raw format for Ed25519. Hoping that ambiguity is clarified in any standardization.

Answer 5 · 2022-06-16T19:29:54.000Z

There's now a WICG draft for Curve25519 and Curve448 in Web Crypto, here. That's being / been discussed in #196, so I'll close this as a duplicate of that issue.