| commit | e0876c3ea39b373c52f27c6b952c2850c21ed19b | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Tue Sep 19 12:17:26 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 19 12:18:31 2023 -0700 |
| tree | 2958bba0d81e2fb7bc1486f80bfef633f203fbb1 | |
| parent | 6d08f81db5130f39ba77270248f9096215ea3933 [diff] |
Support integration of standalone AT library in Chrome With these changes we should be able to move the BlindSignAuth implementation in Quiche to use the standalone Anonymous Tokens library when building in Chrome. In the meantime, this shouldn't break the existing BSA implementation that uses AT exported into Quiche. For reference, how I plan to integrate this with the Chrome codebase can be found in this CL: https://chromium-review.googlesource.com/c/chromium/src/+/4549362 PiperOrigin-RevId: 566707025
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.