ADR 0266 and issue 333: on the control node, agents run under an account of their own #225

Merged

mesh-admin merged 6 commits from decision/0266-agents-run-under-an-account-of-their-own into main 2026-10-09 10:56:11 +00:00

Conversation 2 Commits 6 Files Changed 4

+567 -2

6 Commits

Author	SHA1	Message	Date
jochen	cb907d5810	ADR 0266: an agent can merge its own pull request, and the restart condition's quiet counts on the controller's clock ... The record said a merge needs a person; the forge requires no approval and the merge tool merges once the checks pass, so nothing enforces the operator's yes. What still remains now says so, and that the restart fix counts from when the controller first saw the search pending. Item 10 and routes A and B describe the follow-ups of the review of 2026-10-09.	2026-10-09 12:27:13 +02:00
jochen	d7999e6fc9	ADR 0266: the setuid search's bound is 15 minutes, and the two routes and the restart condition the review of 2026-10-09 found ... Item 10 said two minutes; the engine's bound is 15, with a two-minute limit inside it still to settle. What still remains now names a build from another repository registering a module (mesh-controller 174), the forge's tools changing its protection (mesh-catalog 153), and the urgent condition every engine restart raises (mesh-controller 175).	2026-10-09 11:49:25 +02:00
jochen	ee314a26ca	ADR 0266: say where the boundary stands on 2026-10-09, and the rollout's order ... The routes found around the agent account since the record was written are closed on main (the store's reader, places and served keys, what every session obeys, execute withheld on the control node); the record names them, drops the store gap it said kept the boundary from holding, and says plainly what still remains, first the login shell's execute on the other nodes. To-be 36 §9 gains the prerequisites and the order the parts go out in.	2026-10-09 11:03:27 +02:00
jochen	e215dd95c4	ADR 0266: record the command allow list, the judge's final lists, and the store gap ... The re-review closed the command verb to reads, moved enrolment to the controller's terminal, widened what the node-engine judges, and found the store's reader able to read every secret; say each, and that the boundary is not in force until the store is fixed.	2026-10-09 10:15:47 +02:00
jochen	dbc3ec40e0	ADR 0266: say it detects rather than prevents, and bound what review found ... The review found ways round the record: a verb that set the accounts, root following a link below a home, a tool reading any path as the operator, a restore written beside the agent's files, a stale verdict passing. Record each bound, the exact ways judged and not judged, the guard on every tool and its record's limits, and a rollout order the guard does not block.	2026-10-09 10:15:47 +02:00
jochen	537e5b733b	ADR 0266: on the control node agents run under an account of their own ... The operator chose this remedy for ADR 0259 section 8: an agent there could become root through the operator account's sudo and docker group, and read the tool runner's credential. Record the node fact, the node-engine's judgement the self-check reads, the guard, and how a session starts; issue 333 holds the measured symptom and to-be 36 the design.	2026-10-09 10:15:47 +02:00