7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	b2e2bf0638	Give a channel's verified sender back when the root-free judgement passes again, and say when it is dropped (issue 930) ... A push composed during a failed judgement issued the router a membership without the verified sender and nothing composed it again, so every approval was refused. The self-check now issues it again within one run; a composition says which kind lost it and why.	2026-10-16 17:42:23 +02:00
jochen	eaf5195998	Keep quiet for the setuid search the engine now runs to completion (hq issue 361) ... The node-engine's search has no bound any more: it runs at idle priority and judges from its last complete, fresh result. The controller's quiet while an agent account waits is the engine's rootsearch.Quiet, not the old fifteen-minute bound, and the node-engine is pinned at its pull request.	2026-10-10 00:54:52 +02:00
jschoubben	c544c2a17b	Key root-not-free apart from DA, keep ADR 0266's quiet window there, and judge at one clock (hq ADR 0259 §8) ... The confirmation review of 2026-10-09 found D-root and DA writing one key, machine.<m>.agent-root, from two probes with different words, so it flapped every run; D-root is now root-not-free. D-root raised the urgent condition after every node-engine restart while the first setuid search ran; it now keeps the same quiet window as DA, and the root-free verb still answers that machine not free. agentConfined takes the judging clock.	2026-10-09 13:55:06 +02:00
jschoubben	4c375dafed	Judge a machine root-free only on a positive, fresh measure, and believe a verified sender only there (hq ADR 0259 §8, review H2/H3) ... The agent-root probe read the sudo module's answer, given in the machine's runtime as the very account an agent could become, and took a missing account, a missing answer or no accounts as a pass. One judgement now decides: the machine names an agent account its node-engine judged unable to become root within 15 minutes (agentConfined, mesh-controller #164), and the login shell's execute is not served there; anything not read is not free. The probe raises agent-root on it, the new root-free verb answers it live for the router, and a push composes verified-sender for a kind only while its machine and the router's pass it.	2026-10-09 13:48:56 +02:00
jschoubben	5fa8e40667	Raise agent-root where who can become root is not measured, so the router never reads a missing measure as a no (hq ADR 0259 §8) ... A machine where the router or a verified channel runs and the sudo module is absent or does not answer made the probe fail to run, which raises nothing the router reads, so it went on approving there. Each such machine now raises the same urgent condition, saying it was not measured.	2026-10-09 13:48:56 +02:00
jschoubben	b3fd360ddb	Count the login shell where its execute is served, not where its seat is held (hq ADR 0268) ... The control-node withholds execute through its holder's setting since ADR 0268, so probe D-root read a closed path as open. It now counts the verb as served while the holder's setting for that machine is serve, or the bus hears execute answered there, or the bus could not be asked: a withheld value not yet pushed, or a holder answering against its setting, is never taken for closed.	2026-10-09 13:48:56 +02:00
jochen	9372e80cec	Serve a trusted holder from a runtime of its own account, refuse it in the machine's runtime, and say while an agent can become root where it runs (hq ADR 0259 §8)	2026-10-09 13:48:56 +02:00