From ca8e13a306a2e8bcde1bd4d34b2d56fec3fc6729 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 18 Nov 2026 01:21:30 +0100 Subject: [PATCH] =?UTF-8?q?Answer=20A-485:=20what=20a=20container=20module?= =?UTF-8?q?=20is=20and=20how=20a=20process=20naming=20no=20user=20runs,=20?= =?UTF-8?q?for=20ADR=200680=20=C2=A73?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 0f992846..2471003f 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1967,3 +1967,7 @@ the principle that settles it, cited as "design 47 G A-n". manifest through the seat `mesh-catalog`'s verb `module`. What it keeps on the bus is read from the manifest it answers, or, when it answers none, from the composition this node runs of that build (A-483). (From the develop of A-484.) +- **A-485** (ADR 0680 ยง3; principles 7 and 2) For ADR 0680's rule that a process must be able to read the own secrets + it names: (a) "a container module" is any module with a `container` resource, since a container reads its secrets as + its own account; (b) a process resource that names no `user` runs as root, as the service manager runs it, so it may + read every own secret. (From the develop of ADR 0680 in the manifest validator.) -- 2.54.0