| commit | 9a5d0ecc11a07046ffe9cd376a8acef3db56117c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@chromium.org> | Wed Apr 30 18:23:19 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 30 18:23:19 2025 |
| tree | 53064164c127eb2eba5579269e01d6ee8df992d2 | |
| parent | 3530cedc2e0561ce37125cb87bf850e0086c5c0e [diff] |
Unwind kPostQuantumKyber and kUseMLKEM feature flags Both features have been launched for some time, so we can remove the flags now. (This does not impact the admin policy, just the Chrome-level feature flags.) While I'm here: - Update net/quic/quic_end_to_end_unittest.cc to test by disabling it via config instead of flag. - We no longer need the tri-state optional<bool> in the net stack. - Rename the field from post_quantum_enabled to post_quantum_key_agreement_enabled because presumably we'll eventually have more PQ things to worry about. Fixed: 40910498 Change-Id: I4c1019d7933cc04f72a32fce4ee42fbae620dab2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6497575 Reviewed-by: Dominic Farolino <dom@chromium.org> Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: David Benjamin <davidben@chromium.org> Reviewed-by: Emily Stark <estark@chromium.org> Reviewed-by: Nick Harper <nharper@chromium.org> Cr-Commit-Position: refs/heads/main@{#1454071}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.