This feature adds support for Curve25519 algorithms in the Web Cryptography API, namely the signature algorithm Ed25519
Today web developers are getting around the unavailability of Curve25519 [1] in browser by either including an implementation of its operations in JavaScript or compiling a native one into WebAssembly. Aside from wasting bandwidth shipping algorithms that are already included in browsers that support TLS 1.3, this practice also has security implications, e.g. side-channel attacks as studied by Daniel Genkin et al [2]. [1] RFC 7748, Elliptic Curves for Security [2] Daniel Genkin et al, Drive-By Key-Extraction Cache Attacks from Portable Code.
Docs: https://github.com/WICG/webcrypto-secure-curves/blob/main/explainer.md https://docs.google.com/document/d/1fDTUY3HVAXehi-eSfbi7nxh8ZPw4MpSKM8U1fMdqJlU/edit?usp=sharing
Explainers: https://github.com/tQsW/webcrypto-curve25519/blob/master/explainer.md