You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Policy: driving the Docker API through its socket, or a cgroup release_agent, waits for a person #535
E21's held-out pool has two container-escape moves that the packs let run: the socket calls are only flagged, and the cgroup write is allowed outright:
Raw calls to the Docker socket skip everything the docker command shows a person, and can start a privileged container that mounts the host. Writing a cgroup's release_agent makes the host run a program.
Task: add an ask rule in tracekit/policy2/packs/coding.yaml (its ask section), with a reason and a remedy in the style of its neighbours, that holds:
a request through the Docker or Podman socket: curl, wget, socat or nc naming docker.sock or podman.sock (--unix-socket, UNIX-CONNECT:, -U), and DOCKER_HOST=unix://… set for a command other than docker;
a write (redirection, tee) into release_agent or notify_on_release under /sys/fs/cgroup/.
These must stay allowed (check both engines):
docker ps
docker run --rm hello-world
ls -la /var/run/docker.sock
cat /sys/fs/cgroup/cpu.max
Add the held calls to tests/data/policy/deny/shell.jsonl ("expect": "ask") and the lookalikes to tests/data/policy/benign/shell.jsonl, with a test in tests/test_signer_policy.py.
Keep patterns bounded: tests/test_policy2.py times every pattern on 64 KiB inputs on both engines.
Add the rule to the coding pack's table in docs/policy-v2.md.
Done when: the calls above are held by every pack, E17 adds no false alarm (make eval), tracekit policy lint is clean and make test passes. In the PR, report how many of E21's held-out container-escape calls the server pack now holds.
Comment here to claim it. Commits need a DCO sign-off (git commit -s).
I would like to claim this issue. I'll add the ask rule in tracekit/policy2/packs/coding.yaml to hold Docker/Podman socket calls and cgroup release_agent/notify_on_release writes, add tests and fixtures in deny/benign shell datasets, ensure RE2 bounds and lint pass, update docs, and report the E21 held-out container escape metrics.
@shrinivas-sn Corrected: the packs only flag the Docker socket calls; the cgroup release_agent write is allowed outright (no rule matches it), not flagged.
I'd like to claim this one (first issue for me here).
Plan:
Add one ask rule in coding.yaml, with reason and remedy in the neighbours' style, covering:
curl/wget/socat/nc naming docker.sock or podman.sock (--unix-socket, UNIX-CONNECT:, -U);
DOCKER_HOST=unix://… on a command other than docker;
a redirection or tee into release_agent or notify_on_release under /sys/fs/cgroup/.
Keep the patterns bounded for the 64 KiB timing test on both engines.
Add the held calls to deny/shell.jsonl and the four lookalikes to benign/shell.jsonl, with a test in test_signer_policy.py, and add a row to the coding pack table in docs/policy-v2.md.
Run make test, tracekit policy lint and E17, and report E21's held-out container-escape count for the server pack in the PR.
Disclosure: this work is done by an AI coding agent (Claude Code) operating my account, with a separate AI review pass. The PR will say so.
It's yours, @munjikesh. The gap is still there on main: both socket calls are only flagged in dev, coding and server (strict asks), and the cgroup write is allowed in all four packs. The plan fits. Two notes:
"Done when" asks for every pack, so check which packs read coding.yaml's ask section. A rule only there may not reach server.yaml and strict.yaml.
Activity
shrinivas-sn commentedon Nov 2, 2026
I would like to claim this issue. I'll add the ask rule in tracekit/policy2/packs/coding.yaml to hold Docker/Podman socket calls and cgroup release_agent/notify_on_release writes, add tests and fixtures in deny/benign shell datasets, ensure RE2 bounds and lint pass, update docs, and report the E21 held-out container escape metrics.
LoopGlitch26 commentedon Nov 7, 2026
@shrinivas-sn Corrected: the packs only flag the Docker socket calls; the cgroup
release_agentwrite is allowed outright (no rule matches it), not flagged.LoopGlitch26 commentedon Nov 8, 2026
@shrinivas-sn are you still on this? #544 was closed, and the coding pack has changed since. If you're busy, say so and it opens up for someone else.
LoopGlitch26 commentedon Nov 11, 2026
Opening this up again; thanks for looking.
munjikesh commentedon Nov 11, 2026
I'd like to claim this one (first issue for me here).
Plan:
askrule incoding.yaml, with reason and remedy in the neighbours' style, covering:curl/wget/socat/ncnamingdocker.sockorpodman.sock(--unix-socket,UNIX-CONNECT:,-U);DOCKER_HOST=unix://…on a command other thandocker;teeintorelease_agentornotify_on_releaseunder/sys/fs/cgroup/.deny/shell.jsonland the four lookalikes tobenign/shell.jsonl, with a test intest_signer_policy.py, and add a row to the coding pack table indocs/policy-v2.md.make test,tracekit policy lintand E17, and report E21's held-out container-escape count for the server pack in the PR.Disclosure: this work is done by an AI coding agent (Claude Code) operating my account, with a separate AI review pass. The PR will say so.
LoopGlitch26 commentedon Nov 11, 2026
It's yours, @munjikesh. The gap is still there on main: both socket calls are only flagged in dev, coding and server (strict asks), and the cgroup write is allowed in all four packs. The plan fits. Two notes:
coding.yaml'sasksection. A rule only there may not reachserver.yamlandstrict.yaml.coding.yaml(rules andversion),docs/policy-v2.mdandtests/test_signer_policy.py. Merge main once it lands. If the pack'sversionline conflicts, I'll set the number on your branch.