From 55443b67e62c6753f1a9e4b05765c793c89c35da Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 3 Oct 2026 13:00:35 +0200 Subject: [PATCH] =?UTF-8?q?Design=2038=20WP4:=20what=20the=20review=20of?= =?UTF-8?q?=20mesh-catalog=20#239=20found=20=E2=80=94=20the=20credential?= =?UTF-8?q?=20goes,=20iptables=20is=20declared,=20escalation=20is=20an=20u?= =?UTF-8?q?nchecked=20machine=20fact?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 03-DESIGN/01-to-be/38-building-the-operators-machine.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/03-DESIGN/01-to-be/38-building-the-operators-machine.md b/03-DESIGN/01-to-be/38-building-the-operators-machine.md index e3b4134..ba5ba8a 100644 --- a/03-DESIGN/01-to-be/38-building-the-operators-machine.md +++ b/03-DESIGN/01-to-be/38-building-the-operators-machine.md @@ -201,7 +201,13 @@ broker per node. Two things the package did not say, settled in the module: the run through `sudo` without a prompt where the runtime is not root, since the operator's account may escalate as the operator would; and a bundle has no environment of its own, so the tool reads the filter from the path the manifest's `filtering` names rather than from a variable the container used -to carry. +to carry, a test holding the two together. Three things a review of the change found: the module's +own bus credential and state directory went with the container, since nothing reads them once the +runtime speaks with the node's (the shell module of WP5 declares neither); the `iptables` package the +image used to carry is now declared on the host; and that the operator's account may escalate without +a prompt is a fact about the machine the mesh neither declares nor checks — true on all four today, +and when it is not, the tool names it by how it failed, which is the only check there is until a +record says where the fact belongs. ## WP5 — The shell, on a server first