Chromestatus
unread,1:10 PM (1 hour ago) 1:10 PMSign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to blin...@chromium.org, dad...@google.com, jdeb...@chromium.org, hc...@chromium.org
Contact emails
hc...@chromium.org
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
Web Feature ID
web-cryptography
Goals for experimentation
None
Risks
Interoperability and Compatibility
Won't work cross-browser until other browsers implement any of these new algorithms.
Gecko: Neutral (
https://github.com/mozilla/standards-positions/issues/1282) Despite being neutral, Firefox is shipping anyway
WebKit: Neutral (
https://github.com/WebKit/standards-positions/issues/641) Everyone is neutral because no one likes the Web Crypto API, but everyone agrees we should add PQC to it.
Web developers: No signals
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs,
such that it has potentially high risk for Android WebView-based
applications?
No information provided
Debuggability
No information provided
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
Yes
https://wpt.fyi/results/WebCryptoAPI
DevTrial instructions
https://docs.google.com/document/d/1iFYtR2gab5wDh9DM00BSO8sqPtG6ATWPczmBoD2yLng/edit?usp=sharing
Flag name on about://flags
webcrypto-pqc
Finch feature name
WebCryptoPQC
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/issues/450627017
Launch bug
https://launch.corp.google.com/launch/4463007
Measurement
New Methods:
https://chromestatus.com/metrics/feature/timeline/popularity/5830
https://chromestatus.com/metrics/feature/timeline/popularity/5831
https://chromestatus.com/metrics/feature/timeline/popularity/5832
https://chromestatus.com/metrics/feature/timeline/popularity/5833
https://chromestatus.com/metrics/feature/timeline/popularity/5901
New Algorithms:
https://chromestatus.com/metrics/feature/timeline/popularity/5678,
https://chromestatus.com/metrics/feature/timeline/popularity/5679,
https://chromestatus.com/metrics/feature/timeline/popularity/5680,
https://chromestatus.com/metrics/feature/timeline/popularity/5681,
https://chromestatus.com/metrics/feature/timeline/popularity/5682,
https://chromestatus.com/metrics/feature/timeline/popularity/5683,
https://chromestatus.com/metrics/feature/timeline/popularity/5898,
Estimated milestones
| DevTrial on desktop | 150 |
| DevTrial on Android | 150 |
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5198951632470016
Links to previous Intent discussions
Intent to Prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68e95ca2.2b0a0220.2c868e.0000.GAE%40google.com