Issue 361: the control-node's agent account is never judged, because its search for setuid programs cannot finish in fifteen minutes #261

Merged
mesh-admin merged 3 commits from issues/361-the-control-nodes-agent-account-is-never-judged into main 2026-10-09 23:18:48 +00:00
Contributor

Registers issue 361 (status: located). Do not merge without review.

  • Symptom (2026-10-10 00:43): root-free for the control-node said "not judged (search incomplete): the search for setuid programs did not finish within 15m0s". The router refuses linking on a machine that is not root-free, so phone linking there is blocked.
  • Cause: the node-engine bounded the whole search at 15 minutes (rootsearch.Bound), kept its result in memory only, and the controller's quiet was the same value. A machine whose walk takes longer is never judged.
  • Fix (open): mesh-host #75 (resumable walk in the engine, idle priority, no bound, verdict only from a complete search younger than 36 h, kept across restarts, daily and after an apply that moved root's things) and mesh-controller #190 (quiet = rootsearch.Quiet, 12 h). The diagnosis records the values and why 36 h rather than 26 h, what stays open (first walk not measured, BFQ for the idle class, an ask to search again not kept across a restart, ADR 0266 progressive insight on resolution, replay), and fanotify FAN_ATTRIB as a later option.

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

Registers issue 361 (status: located). Do not merge without review. - **Symptom (2026-10-10 00:43):** `root-free` for the control-node said "not judged (search incomplete): the search for setuid programs did not finish within 15m0s". The router refuses linking on a machine that is not root-free, so phone linking there is blocked. - **Cause:** the node-engine bounded the whole search at 15 minutes (`rootsearch.Bound`), kept its result in memory only, and the controller's quiet was the same value. A machine whose walk takes longer is never judged. - **Fix (open):** mesh-host #75 (resumable walk in the engine, idle priority, no bound, verdict only from a complete search younger than 36 h, kept across restarts, daily and after an apply that moved root's things) and mesh-controller #190 (quiet = `rootsearch.Quiet`, 12 h). The diagnosis records the values and why 36 h rather than 26 h, what stays open (first walk not measured, BFQ for the idle class, an ask to search again not kept across a restart, ADR 0266 progressive insight on resolution, replay), and fanotify `FAN_ATTRIB` as a later option. Checks run locally: records.py, index.py, cycle.py, words.py (with the catalogue's list) all pass.
mesh-admin added 1 commit 2026-10-09 23:03:59 +00:00
Issue 361: the control-node's agent account is never judged, because its search for setuid programs cannot finish in fifteen minutes
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 superseded: a newer head of the same pull request
c0c7515e06
Author
Contributor

Delivery novox/hq@94719d4662cf — delivered since 2026-10-09T23:19:03Z

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

Transitions

  • 2026-10-09 23:12 (new) → proposed (announced): novox/hq#261's head announced
  • 2026-10-09 23:13 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 23:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 23:19 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:19 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@94719d4662cf` — **delivered** since 2026-10-09T23:19:03Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-09 23:12 (new) → proposed (announced): novox/hq#261's head announced - 2026-10-09 23:13 proposed → checked (checked): the verdict names this commit - 2026-10-09 23:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 23:19 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:19 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`.
jschoubben added 1 commit 2026-10-09 23:12:05 +00:00
Issue 361: record the review of the fix and what it changed
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 superseded: a newer head of the same pull request
46f89cd102
jschoubben added 1 commit 2026-10-09 23:12:22 +00:00
Issue 361: say when a search runs as the fix does it
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
94719d4662
mesh-admin merged commit 511cea04f2 into main 2026-10-09 23:18:48 +00:00
mesh-admin deleted branch issues/361-the-control-nodes-agent-account-is-never-judged 2026-10-09 23:18:48 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#261