Answer A-485: what a container module is and how a process naming no user runs, for ADR 0680 §3
This commit is contained in:
@@ -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
|
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
|
answers, or, when it answers none, from the composition this node runs of that build (A-483). (From the develop of
|
||||||
A-484.)
|
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.)
|
||||||
|
|||||||
Reference in New Issue
Block a user