vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

say that the backend env leaf and file are agent-writable, and why that is accepted

Browse source
This commit is contained in:
atlas 2026-10-27 22:12:52 +01:00
commit be3a3af093
1 changed files with 22 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

9
swarm-secret-client/src/policy.rs
View file

@ -205,8 +205,13 @@ const ENTITY_NAME_TEMPLATE: &str = "{{identity.entity.name}}";
///
/// The one write is `create` on the agent's own [`backend_env`] leaf, without
/// `update`: the agent seeds it from the file it has today, once, and cannot
/// replace it. Any other write would let an agent hand itself an identity it
/// was never issued. An agent has no business with another agent's
/// replace it. The stanza cannot constrain the content, and the agent's own
/// process holds the identity, so while the leaf is empty it can also create it
/// with any text, and the store's value then wins over the file. That is no
/// wider than the harness-dir file the agent already owns:
/// `nix/agent-modules/user.nix`'s `heal_own_dir` chowns that dir to the agent at
/// every activation, a gap the issue tracker has an open bug for. Any other
/// write would let an agent hand itself an identity it was never issued. An agent has no business with another agent's
/// credentials, a hive's, a service's, or the controller's, so none of
/// [`render_shared_hives`]'s breadth applies. A hive still reads this
/// agent's secrets, and closing that is its own decision.