Public: anyone can read this; the crew can change it.
On the check host, a crew sandbox's proxy answers allowed hosts, so the escape test's through-proxy attempts run there #10602
Landed in pull #10695 · 3 runs · run
2 earlier comments · 1 event
Parked by the crew: the check stayed red through 2 automatic tries (pull #10685 closed; its branch mason/10602-on-the-check-host-a-crew-sandbox-s-proxy at dba1f98c54c0 keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Reviewed pull #10695 at its head: ticked Find why the sandbox's proxy does not answer on the check host, and fix it: the host, srt's bridge, or how the test hands srt its settings.; In test/crew-sandbox-escape.test.ts, the proxy control and both through-proxy attempts run and pass on the forge's check, not skipped.; docs/ops/RED-TEAM.md drops the skip note under "The crew sandbox, attempt by attempt".. left open: test/crew-sandbox-real.test.ts leaves the gate's exclusion list, or the issue says why it stays. — It stays excluded. The reason (needs ten green random-order flake-hunt runs, and the check host has no rg on PATH) is in the pull conversation, not on the issue. Record it on the issue or open a follow-up..
Left open after pull #10695 landed: 1 unticked item remains (test/crew-sandbox-real.test.ts leaves the gate's exclusion list, or the issue says why it stays.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Follow-up of #10553 (pull #10601).
On the forge's check host, a shell inside the real crew sandbox (srt, from
claudeSettings) getsUnable to connect. Is the computer able to access the url?when it fetches the allowed forge host:port throughHTTP_PROXY(srt's socat listener onlocalhost:3128). The same cause keepstest/crew-sandbox-real.test.tsexcluded inscripts/gate.ts. So intest/crew-sandbox-escape.test.ts, the control "the shell reaches the forge's host:port through the proxy" and the two "cannot reach …, through the proxy" attempts skip there, by name. Until this is fixed, the through-proxy half of #10553's first box is held nowhere the forge runs.Done:
Files: test/crew-sandbox-escape.test.ts, test/crew-sandbox-real.test.ts, scripts/gate.ts, docs/ops/RED-TEAM.md