commit | 54f21233321b7a5ef64386f2dc11156039ae32a4 | [log] [tgz] |
---|---|---|
author | dschinazi <dschinazi@google.com> | Tue Dec 03 13:46:46 2024 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Dec 03 13:47:30 2024 -0800 |
tree | 206fc23248e5ec653897968def06192c3154f29e | |
parent | 51484c694f99d211587d24e5d3e2634b12f978f6 [diff] |
Chaos Protection v2 This CL adds support for multi-packet chaos protection. While the first version of Chaos Protection would scramble the ClientHello if it fit in a CRYPTO frame in a single packet, the emergence of post-quantum cryptography has now caused the ClientHello to span multiple packets. Chaos Protection v2 now scrambles the ClientHello across packets, such that it is now required to parse all of them in order to extract information such as the SNI. This CL also removes automatic flushing of initial crypto packets in the packet creator. This is safe because all uses of such functions are guaranteed to use a scope packed flusher anyway. Note that --quic_enable_new_chaos_protector is still marked as enabled_blocked_by so it is safe to add new functionality behind it. Protected by FLAGS_quic_enable_new_chaos_protector. PiperOrigin-RevId: 702456667
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.