Let a trusted file that names its keys hold only those keys at the terminal (hq issue 586, ADR 0329 §5)
mesh/merge-gate out of date: judged against trunk 454a3db69a1e, the trunk is now 4473bc7d7315; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against trunk 454a3db69a1e, the trunk is now 4473bc7d7315; judged again on a recheck or when it is merged
mesh/delivery superseded: a newer head of the same pull request

A module with a trusted mergeable file had its whole layer refused through the
settings verb, because such a file took any key. Once a module's files name the
keys they take (ADR 0326), each file takes only those, so only a trusted file's
named keys are the terminal's: betterbird's tags, in a file nothing trusts, is set
through the verb, while its accounts and identities stay the terminal's or the
operator's warrant. A module whose files name no keys keeps the whole-layer rule.
This commit is contained in:
jochen
2026-10-13 02:03:12 +02:00
parent 454a3db69a
commit 3379ab3b61
4 changed files with 79 additions and 1 deletions
+1
View File
@@ -38,3 +38,4 @@
./cmd/mesh-controller TestReplay201ThePlansSend
./internal/inventory TestAWalksRestIsReadFromEachMachinesOwnSend
./internal/inventory TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed
./cmd/mesh-controller TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb