| commit | b250a44acf2e39f9f40534f8076c6f09a5b02b09 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Mon Jan 08 21:06:38 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 08 21:08:03 2024 -0800 |
| tree | ffd8fe3fe0788959467c2a92ff2073ce149e82d9 | |
| parent | 4f01b0915e0d5a1990db6f55eb7b65c97b2a7045 [diff] |
Removing key validity start and end time checks from rsa bssa sign client as we do not want clients to err if their clocks are incorrect and in turn crash chrome processes. Moreover, we are already doing these validity checks on the server at signing time. Removing a outdated test from GFE codebase. PiperOrigin-RevId: 596788967
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.