On Wed, Jun 17, 2026 at 9:48 AM Mike Taylor <[email protected]> wrote:

> On 6/17/26 9:38 a.m., Chromestatus wrote:
>
> *Contact emails*
> [email protected]
>
> *Explainer*
> *No information provided*
>
> *Specification*
> https://wicg.github.io/webcrypto-modern-algos
>
> *Summary*
> Add post-quantum cryptography and a common symmetric AEAD to the set of
> cryptographic algorithms available in the Web Cryptography API. This will
> enable developers to have access browser-provided implementations of common
> quantum-resistant cryptographic algorithms standardized by NIST. * ML-KEM -
> 768, 1024 * ML-DSA - 44, 65, 87 * ChaCha20-Poly1305 * X-Wing
>
> *Blink component*
> Blink>WebCrypto
> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebCrypto%22>
>
> *Web Feature ID*
> web-cryptography <https://webstatus.dev/features/web-cryptography>
>
> *TAG review*
> *No information provided*
>
> *TAG review status*
> Pending
>
> *Goals for experimentation*
> None
>
> Can you say more why you want to run an OT (or is this a Finch stable
> experiment) instead of just shipping
>

We'd like to get a few sites to test out the new algorithms in real-world
scenarios before shipping it, to ferret out any subtle bugs that might've
slipped past us. The WPTs test are extensive, but we've already caught a
few bugs that slipped in during the development process (e.g.
crbug.com/512509718, a JWK export/import bug for ML-KEM fixed by
crrev.com/c/7887900), and we'd like to prevent oddities from getting baked
into our implementation because we missed something (an old historical
example: https://issues.chromium.org/issues/40365706).

Ensuring that the algorithms are cryptographically correct is not as big of
a worry (as we're using BoringSSL's implementation of the crypto).
Performance is also not a huge concern, but it would be good to get this
evaluated with in-the-world usage.

/hubert

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHEiSH0dYnOrh6wJrog4bgpcofiDQMi7%3D%3DUOM7rHPi9FKeaVdA%40mail.gmail.com.

Reply via email to