Google Git
Sign in
quiche/quiche/1127ea96ae32bba238683333f512bf9ff929354c
commit
1127ea96ae32bba238683333f512bf9ff929354c
[log]
author
QUICHE team <quiche-dev@google.com>
Wed Jul 01 09:48:13 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Jul 01 09:48:48 2026 -0700
tree
7011e57f4a08b2e2f597835463cce58fd30c1b97
parent
aeaa7694e802af3d09131eba33ace65c43e0ee40 [diff]
[SM][iOS] CL 1/n: Refactor BlindSignAuth to accept generic attestation data (v2)

- Refactor BlindSignAuth to accept google::protobuf::Any for attestation data to enable cross-platform compatibility.

- Please Note: This is v2 of the CL. The original CL (cl/934771494) was rolled back because it broke postsubmit compilation for `pricli` targets (under //security/oak/tools/pricli). The breakage occurred because `pricli` was still using the old V1 callback signature (expecting absl::Span<const std::string>) while the CL refactored it to expect google::protobuf::Any.

- This v2 CL fixes the breakage by updating `pricli` (token_fetcher.cc and BUILD) to wrap its attestation data in `google::protobuf::StringValue` and pack it into the `Any` proto, resolving the compilation mismatch.

- Tested and verified that all pricli and BlindSignAuth tests pass:
Sponge Link: http://sponge2/e463c14f-ba7e-4eef-94cd-5c93ee68d3d7

#sm-ios

PiperOrigin-RevId: 941150217
4 files changed
tree: 7011e57f4a08b2e2f597835463cce58fd30c1b97
  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.

Build and run standalone QUICHE

QUICHE has binaries that can run on Linux platforms.

Follow the instructions to install Bazel.

sudo apt install libicu-dev clang lld
cd <directory that will be the root of your quiche implmentation>
git clone https://github.com/google/quiche.git
cd quiche
CC=clang bazel build -c opt //...
./bazel-bin/quiche/<target_name> <arguments>

There are several targets that can be built and then run. Full usage instructions are available using the --helpfull flag on any binary.

  • quic_packet_printer: from a provided packet, parses and prints out the contents that are accessible without decryption.

Usage: quic_packet_printer server|client <hex dump of packet>

  • crypto_message_printer: dumps the contents of a QUIC crypto handshake message in a human readable format.

Usage: crypto_message_printer_bin <hex of message>

  • quic_client: connects to a host using QUIC and HTTP/3, sends a request to the provided URL, and displays the response.

Usage: quic_client <URL>

  • quic_server: listens forever on --port (default 6121) until halted via ctrl-c.

  • masque_client: tunnels to a URL via an identified proxy (See RFC 9298).

Usage: masque_client [options] <proxy-url> <urls>

  • masque_server: a MASQUE tunnel proxy that defaults to port 9661.

Usage: masque_server

  • web_transport_test_server: a server that clients can connect to via WebTransport.

  • moqt_relay: a relay for the Media Over QUIC transport for publishers and subscribers can connect to.

Usage: moqt_relay

Logging

Most log messages in QUICHE use the QUICHE_DLOG macro. In standalone quiche, these all either go to stderr, or are suppressed, based on the --stderrthreshold flag.

To send INFO level log messages to a file, you would therefore invoke

<binary> <args> > <logfile> 2>&1

Use the --helpfull flag for more.