tls-forge
Copyright 2026 Ihar Kazlouski

This product includes software developed by Ihar Kazlouski.

Licensed under the Apache License, Version 2.0 (the "License"); see LICENSE.
Section 4 of that licence obliges anyone who copies, modifies or redistributes
this work — in source or binary form, and an npm package containing a compiled
binary is a binary form — to retain the copyright notice above and to carry this
NOTICE file with it.


WHAT IS NOT COVERED BY THE GRANT
--------------------------------

Some files in this tree are recordings of another program's output rather
than the author's work, and the Apache-2.0 grant above is not a claim over
them:

  testdata/chrome151-clienthello.bin
  testdata/chrome155-clienthello.bin
  testdata/chrome155-clienthello-resumed.bin
  testdata/chrome155-http2-preamble.bin
      TLS ClientHellos, cold and resumed, and the start of an HTTP/2
      connection, as Google Chrome 151 and 155 put them on the wire, captured
      on the author's own machine and kept as test fixtures. They are
      protocol messages — measurements of what a program sent — not copies of
      that program.

  testdata/chrome155-requests.json
  testdata/chrome155-decoding.json
  testdata/chrome155-ech.json
      What Google Chrome 155 was measured sending and doing, on the author's
      own machine: the requests it made in each scenario, how it decoded each
      body, and the lengths it drew. testdata/README.md says how each was
      measured.

  profile/data/chrome_151/ to profile/data/chrome_155/, each of
  linux.json, macos.json and windows.json
      A ClientHello together with the HTTP/2 settings, header order,
      user-agent string and, where they were measured, client hints observed
      from one version of the browser, one file per platform. The user-agent
      strings are Google's; the rest is measurement.

None of these files contains any part of Chrome, and nothing here is endorsed by
or affiliated with Google. Everything else in the tree — the library, the echo
server, the command line, the Node client, the tests and the prose — is the
author's work and is covered by LICENSE.


THIRD-PARTY SOFTWARE
--------------------

tls-forge compiles to a single static binary, so its dependencies travel inside
it — including inside the binaries published in the npm packages. Their licences
are reproduced in full in THIRD-PARTY-NOTICES.txt, which must travel with any
distributed copy for the same reason this file must.

One of them is worth naming here. github.com/igor-lemon/fhttp, tls-forge's fork
of github.com/bogdanfinn/fhttp, is a fork of the Go standard library's net/http,
and carries the Go licence that bogdanfinn/fhttp's sources name and it ships
none of.
