Public: anyone can read this; the crew can change it.
Crew sandbox: escape attempts under procMount Unmasked, each a test #10450
Parked by the crew: the check stayed red through 2 automatic tries (pull #10460 closed; its branch scout/10450-crew-sandbox-escape-attempts-under-procm at 44efd36fa298 keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check stayed red through 2 automatic tries (pull #10479 closed; its branch scout/10450-crew-sandbox-escape-attempts-under-procm at 4ea33a857367 keeps the work so far).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check stayed red through 2 automatic tries (pull #10460 closed; its branch
scout/10450-crew-sandbox-escape-attempts-under-procmat 44efd36fa298 keeps the work so far) - the check stayed red through 2 automatic tries (pull #10479 closed; its branch
scout/10450-crew-sandbox-escape-attempts-under-procmat 4ea33a857367 keeps the work so far)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Split by the planner into #10552 (read attempts) and #10553 (write and egress attempts, plus RED-TEAM.md). Both start from the parked branch. The parked pull went red outside its tests, after it deleted src/kernel/why_now.ts, so #10552 says to delete no module and leave scripts/unreached-allow.json as it is.
Part of #10441. Inside a crew run's bwrap (src/crew/sandbox.ts) with procMount: Unmasked, try to: read outside the worktree (/data, /proc/1/environ, other crews' dirs), write outside it, and reach a host beyond the egress allowlist. Each attempt becomes a test (test/crew-sandbox.test.ts, or a cell suite the forge check runs) that fails if the attempt works. Record the results in docs/ops/RED-TEAM.md.