The interop suite proves the protocol against a bridge the test starts
itself. Nothing proved the deployed one, and the gap is not academic: a
container reporting "Up" establishes that a process is running, not that
its published line is dialable from outside, not that the handshake
completes against the Tor Project's own client, and not that whatever it
fronts still answers.
bridgecheck takes a bridge line exactly as an operator receives it,
dials with real lyrebird, and speaks HTTP through the tunnel. Used to
verify the first deployed bridge today:
handshake: OK against real lyrebird
upstream: HTTP 200 OK via 135.148.121.177:8443
server: flamenet-relay
The Server: header is the part that matters — that is the relay
answering from behind the bridge, so the whole path is proven rather than
the socket being open.
⚠️ Deliberately not wired into any test suite. It needs a live bridge and
the network, so putting it in CI would produce exactly the flaky, ignored
job that teaches people to stop reading test results.
The interop suite proves the protocol against a bridge the test starts
itself. Nothing proved the deployed one, and the gap is not academic: a
container reporting "Up" establishes that a process is running, not that
its published line is dialable from outside, not that the handshake
completes against the Tor Project's own client, and not that whatever it
fronts still answers.
`bridgecheck` takes a bridge line exactly as an operator receives it,
dials with real lyrebird, and speaks HTTP through the tunnel. Used to
verify the first deployed bridge today:
handshake: OK against real lyrebird
upstream: HTTP 200 OK via 135.148.121.177:8443
server: flamenet-relay
The `Server:` header is the part that matters — that is the relay
answering from behind the bridge, so the whole path is proven rather than
the socket being open.
⚠️ Deliberately not wired into any test suite. It needs a live bridge and
the network, so putting it in CI would produce exactly the flaky, ignored
job that teaches people to stop reading test results.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The interop suite proves the protocol against a bridge the test starts
itself. Nothing proved the deployed one, and the gap is not academic: a
container reporting "Up" establishes that a process is running, not that
its published line is dialable from outside, not that the handshake
completes against the Tor Project's own client, and not that whatever it
fronts still answers.
bridgechecktakes a bridge line exactly as an operator receives it,dials with real lyrebird, and speaks HTTP through the tunnel. Used to
verify the first deployed bridge today:
The
Server:header is the part that matters — that is the relayanswering from behind the bridge, so the whole path is proven rather than
the socket being open.
⚠️ Deliberately not wired into any test suite. It needs a live bridge and
the network, so putting it in CI would produce exactly the flaky, ignored
job that teaches people to stop reading test results.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
assigned to @paulhitt
mentioned in commit
8ad485465a