Google Git
Sign in
quiche / quiche / dc5dd128ae9b7790323db73c5a33ce698e1d843e
commitdc5dd128ae9b7790323db73c5a33ce698e1d843e[log] [tgz]
authordmcardle <dmcardle@google.com>Fri Oct 24 14:37:25 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Fri Oct 24 14:38:25 2025 -0700
tree0539369642b1dffa83fbc8f224b0e576bdd10ae8
parent2b095018bb17fddee27919fa310a33602a019873 [diff]
Add fuzz tests for SNI normalization and validity properties in QuicheHostnameUtils

Primarily, this tests that NormalizeHostname() is idempotent for hostnames where IsValid() returns true. It also tests that normalizing a valid hostname produces another valid hostname.

If normalization is not idempotent, we'd have to think carefully about whether the server ever normalizes incoming SNIs twice.

If normalization does not preserve validity, we'd have to make sure the client checks validity after normalization. (Otherwise, a client could send what they believe is a valid SNI, only for the server to reject it post-normalization.)

PiperOrigin-RevId: 823669504
1 file changed
tree: 0539369642b1dffa83fbc8f224b0e576bdd10ae8
  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