Research 041: the agent's session runs confined, instead of being proven by a disk-wide search #262

Merged
mesh-admin merged 1 commits from research/041-the-agents-session-runs-confined into main 2026-10-09 23:07:33 +00:00
Contributor

Opens research 041 (status: active). Do not merge without review.

Why. ADR 0266 §3 item 10 judges the agent account by a search of every local filesystem for setuid programs no package owns. On the control-node it did not finish within its 15-minute bound (measured 2026-10-10 with mesh-controller.root-free), so the account is not judged, agent-root and root-not-free are open, and ADR 0259 §8 honours no approval proven there; linking the operator's phone channel is blocked. A resumable search is the short-term fix, tracked separately.

What the effort asks. Whether the agent's session should instead start confined: no_new_privs (so setuid, setgid and file capabilities grant nothing), a confined view of the files (service manager unit vs Landlock vs bubblewrap, and what Claude Code's own sandbox covers), and everything else through mesh tools (no seat reads a file, lists a directory or reads a non-unit log today). Then what must be proven for root-free (the doors into the account, plus every process of the account carrying NoNewPrivs: 1 in a confined unit, read from /proc), what becomes of the setuid search, and what it does not cover (the mesh MCP server without a login of its own, kernel exploits).

Documents. 00-overview.md; 01-options-and-open-questions.md with the comparison, the proof, five open questions for the operator with recommendations, and the next measurements. Kernel and tool behaviour is from documentation and marked to measure.

Checks run locally: records.py, index.py, cycle.py, words.py all pass (words.py without the catalogue's list).

Opens research 041 (status: active). Do not merge without review. **Why.** ADR 0266 §3 item 10 judges the agent account by a search of every local filesystem for setuid programs no package owns. On the control-node it did not finish within its 15-minute bound (measured 2026-10-10 with `mesh-controller.root-free`), so the account is *not judged*, `agent-root` and `root-not-free` are open, and ADR 0259 §8 honours no approval proven there; linking the operator's phone channel is blocked. A resumable search is the short-term fix, tracked separately. **What the effort asks.** Whether the agent's session should instead start confined: `no_new_privs` (so setuid, setgid and file capabilities grant nothing), a confined view of the files (service manager unit vs Landlock vs bubblewrap, and what Claude Code's own sandbox covers), and everything else through mesh tools (no seat reads a file, lists a directory or reads a non-unit log today). Then what must be proven for root-free (the doors into the account, plus every process of the account carrying `NoNewPrivs: 1` in a confined unit, read from `/proc`), what becomes of the setuid search, and what it does not cover (the mesh MCP server without a login of its own, kernel exploits). **Documents.** `00-overview.md`; `01-options-and-open-questions.md` with the comparison, the proof, five open questions for the operator with recommendations, and the next measurements. Kernel and tool behaviour is from documentation and marked *to measure*. Checks run locally: records.py, index.py, cycle.py, words.py all pass (words.py without the catalogue's list).
mesh-admin added 1 commit 2026-10-09 23:04:21 +00:00
Research 041: the agent's session runs confined, instead of being proven by a disk-wide search
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
4bc0919102
The setuid search did not finish within its bound on the control-node, so no
approval proven there is honoured; a confined start may answer the question
ADR 0259 asks directly, at a cost that does not grow with the disks.
Author
Contributor

Delivery novox/hq@4bc0919102ef — delivered since 2026-10-09T23:07:59Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-09 23:04 (new) → proposed (announced): novox/hq#262's head announced
  • 2026-10-09 23:05 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 23:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 23:07 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-09 23:07 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@4bc0919102ef` — **delivered** since 2026-10-09T23:07:59Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-09 23:04 (new) → proposed (announced): novox/hq#262's head announced - 2026-10-09 23:05 proposed → checked (checked): the verdict names this commit - 2026-10-09 23:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 23:07 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-09 23:07 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-admin merged commit 288da29d94 into main 2026-10-09 23:07:33 +00:00
mesh-admin deleted branch research/041-the-agents-session-runs-confined 2026-10-09 23:07:33 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#262