| commit | 86c7cec5fa5434b26587a594bbcea3628ac87c74 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Thu Mar 23 15:51:07 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 23 15:51:56 2023 -0700 |
| tree | 927e60fd5ca593c1a54a8ce19540ac92fd6a46c9 | |
| parent | e3e1e8bb43998868122c9747af56622921df2bd4 [diff] |
Updating PublicMetadataHashWithHKDF function according to the latest IETF draft before we use it in prod. Adding the latest test vectors as well. This CL also makes sure that openssl RSA struct is not used as storage for the exponent augmented with the public metadata in blinder as well as the verifier in third_party/anonymous_tokens/cpp/crypto. These changes will let us enable public metadata support in prod in follow-up CLs as well as accept empty public metadata as a valid value when public metadata support in enabled. PiperOrigin-RevId: 518984326
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.