Description
Parent
What to build
A maintainer runs an opt-in variant of the Compose demo that puts a real Squid between the Gateway and the site, and its --verify mode proves the bytes took the proxied path. It is run by hand before a release, as the Compose demo is today; no workflow runs it. The default walkthrough stays as it is.
In the variant the Gateway shares a network with the Broker and Squid, and the site is on a network only Squid shares, so the Gateway has no direct route to the site. Squid allows CONNECT only to the site's hostname and port and does no TLS interception.
--verify drives the real Companion and browser as it does today, then correlates three observations from that one run: Squid's access log line for the CONNECT, the certificate fingerprint the site saw, and the response the Workload read.
The failure checks reuse the grant approved in that run, so they need no second approval. While the grant is live the launcher, in turn: swaps Squid's ACL to refuse the site and reloads it, restores the ACL and stops the site, then stops Squid. After each, the Workload repeats its request.
Running it needs Docker, the Companion and a desktop session or a virtual display.
Acceptance criteria
- The demo launcher has an opt-in Squid variant, and the default walkthrough's services, networks and behaviour are unchanged
- In the variant the Gateway shares a network with the Broker and Squid, and the site is on a network only Squid shares
- Squid runs from an image pinned by digest, allows
CONNECTonly to the site's hostname and port, and does no TLS interception - From one
--verifyrun, Squid's access log shows a successfulCONNECTto the site's hostname and port, the fingerprint the site returned equals the one approved in the Companion, and the Workload read the site's response - With that grant live and Squid's ACL swapped to refuse the site and reloaded, the Workload's request fails with
proxy_denied, and Squid's log shows the refusal - With that grant live, the ACL restored and the site stopped, the Workload's request fails with
upstream_failure - With that grant live and Squid stopped, the Workload's request fails with
proxy_unavailable - The operator guide's example Squid ACLs are taken from the configuration that passed: allow by hostname and port, block metadata, link-local and loopback addresses, and pin a private site to its prefixes
- The developer guide says how to run the variant and names the Squid version it was qualified against
- The output of a passing
--verifyrun of the variant is recorded on this ticket
Decided in: #49 (spec); ADR 0003; the triage outcome on #46
Live step at merge: comment on #46 pointing the reporter at the documented Compose configuration, so they can repeat it on Fargate (whoever merges)
Activity
sodre commentedon Nov 22, 2026
A passing
--verifyrun of the Compose demo's Squid variant, on5d76a8b(#55's branche2/49-egress-proxy), Linux arm64, Squid 6.14 fromubuntu/squid:6.6-24.04_edge@sha256:d9c34c5ab74c6dd41cf1070d9b4221aac072e67e983527ca2d41512958f77506:dbus-run-session -- xvfb-run -a .venv/bin/python examples/demo-integrator/compose_demo.py --squid --verify \ --app "$PWD/packages/companion/dist/linux-arm64-unpacked/countersign-companion"Its check lines (the rest of its output is Compose and the virtual desktop session); it exited 0:
An earlier run on
17525c6, before the review's fixes, passed the same checks.