[SM] CL 1/n: Refactor BlindSignAuth to accept generic attestation data - Refactor BlindSignAuth to accept `google::protobuf::Any` for attestation data to enable cross-platform compatibility. - By replacing the `absl::Span<const std::string>` parameter (which was previously used to pass Android-specific attestation certificates) with a generic `Any` protobuf, we decouple the core QUICHE library from platform-specific attestation structures. The responsibility of constructing the platform-specific proto (e.g., `AndroidAttestationData` for Android or `IosAttestationData` for Apple devices) is now correctly delegated to the platform-specific callers (like the Android JNI layer). - It was chosen to refactor the interface rather than introducing method overloads (i.e. maintaining the old Android signature alongside a new iOS signature) to keep the core `BlindSignAuth` library clean and fully platform-agnostic. Overloading would require the core library to continue parsing and depending on Android-specific protos. The chosen approach enforces a cleaner separation of concerns, ensuring that the core library only acts as a pass-through for opaque `Any` payloads. #SM PiperOrigin-RevId: 934771494
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.
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.
Usage: quic_packet_printer server|client <hex dump of packet>
Usage: crypto_message_printer_bin <hex of message>
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>
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
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.