Google Git
Sign in
quiche/quiche.git/56eaa1e736c3506dab2a98e99c43e25e5ecf71bb
commit
56eaa1e736c3506dab2a98e99c43e25e5ecf71bb
[log]
author
QUICHE team <quiche-dev@google.com>
Wed Aug 20 15:07:59 2025 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Aug 20 15:09:11 2025 -0700
tree
9827fa38f10f1f330cfb9fae2563777ecc8679db
parent
df7f7ece0bc5d00f265f55ced0b1e375ce214f90 [diff]
Add BoringSSL API_VERSION guard around SSL_CREDENTIAL call

TlsServerConnection::SetCertChain() had a BoringSSL version guard around the call to set the trust anchor IDs. This change puts the adjacent SSL_CREDENTIAL calls behind the same version guard.

Thanks to Dimitri John Ledkov for the change; see https://github.com/google/quiche/pull/93.

This does not affect production GFE because GFE's already on an up-to-date BoringSSL.

PiperOrigin-RevId: 797480658
1 file changed
tree: 9827fa38f10f1f330cfb9fae2563777ecc8679db
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. .bazelversion
  6. BUILD.bazel
  7. CONTRIBUTING.md
  8. LICENSE
  9. MODULE.bazel
  10. MODULE.bazel.lock
  11. README.md
  12. WHITESPACE
README.md

QUICHE

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.