Update fuzzer Packet/Proto Conversion to use 16B auth tags.

Virtually all packets (including all IETF QUIC packets) have 16B tags, so the fuzzer packet signature should match that.

Also, packets with very small payloads, once enabled, cannot work with short tags, so longer tags are a prerequisite.

The test was originally highly dependent on everything being a NullEncrypter, so that decryption would work even if things were out of sync. This now normalizes everything so that Initial packets are always sent with the version-appropriate encryption, which might involve the original Destination Connection ID, and all other encryption levels are sent with the TaggingEncrypter.

Some production code, when operating in fuzz mode, used the NullDecrypter for Forward Secure packets. This can't explicitly be replaced with TaggingDecrypter, since this is in the test namespace. So instead, this adds a singleton to ssl_global_data to refer to a factory in the test namespace.

PiperOrigin-RevId: 491481742
2 files changed
tree: eaa49af4b6690c6653591d800d58ac552ad4d80f
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. BUILD.bazel
  8. README.md
  10. WORKSPACE.bazel


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.