| commit | bc02673d9ea4937cfec65dee62e95a9fca31239b | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Tue Apr 26 17:51:01 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 26 17:52:02 2022 -0700 |
| tree | 378e24289bd122ebff58a1dcec5014bb5b863ae0 | |
| parent | 007fae4879762ee1bbf099b5c13b09a7e29c8e45 [diff] |
Split out google3-specific bits of crypto_test_utils into //net/quic. This CL does the following things: (1) It introduces a default implementation of ProofSourceForTesting and ProofVerifierForTesting. (2) google3-specifc versions are now available via ProofSourceForTestingGoogle3() and ProofVerifierForTestingGoogle3(). (3) google3 embedders outside of QUICHE are changed to use those as apporpriate. PiperOrigin-RevId: 444716512
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.