| commit | efdd7dabb32c7ed6ca5083734ac7f324dacec028 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Tue Oct 15 10:22:15 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 15 10:23:21 2024 -0700 |
| tree | e9eb5b696ec0511954e40f7240b7145102c18e6b | |
| parent | 2667ac9520c38faef907d8a31c575b580969d5ef [diff] |
Enable stack protector to prevent stack buffer overflows. Fix QUIC build _FORTIFY_SOURCE=2 for arcore, note Chrome OS did a simular fix to cl/530360898 no change in functionally This will cost ARCore +274.4k http://go/arcore-size-reports/stack_canary_fortify To know more about how this was tried and sign of see. go/memory-request-stack-canary-fortify-in-arcore go/arcore-fortify-and-jni PiperOrigin-RevId: 686151450
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.