| commit | f605b8327e06b3b4e8b25499d65798c9a3ae6e9a | [log] [tgz] |
|---|---|---|
| author | davidben <davidben@google.com> | Tue Apr 15 13:02:37 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 15 13:03:36 2025 -0700 |
| tree | b302cd434b7ca8374518783472d4996df862ace9 | |
| parent | cfe837e3581c47701a2697659f51b098f70fc77c [diff] |
Remove now unnecessary BORINGSSL_API_VERSION ifdefs At the time these codepaths were added, the APIs were new and we still needed to accommodate older BoringSSL. This is no longer a concern. While I'm here, switch the supported groups test from Kyber (pre-standard) to ML-KEM (standard). PiperOrigin-RevId: 747990095
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.