state the heal_own_dir cause in the backend env comments
This commit is contained in:
parent
be3a3af093
commit
ca194f5c91
1 changed files with 9 additions and 7 deletions
|
|
@ -21,8 +21,9 @@
|
|||
# The leaf's create grant cannot constrain content, so while the leaf is empty
|
||||
# the agent's own process can also create it with any text, and the store's
|
||||
# value then wins over the file. That is no wider than the file the agent
|
||||
# already owns: `./user.nix`'s `heal_own_dir` chowns the harness dir to the
|
||||
# agent at every activation, a gap the issue tracker has an open bug for.
|
||||
# already owns: the container activation's `heal_own_dir` (`./user.nix`)
|
||||
# re-owns the harness dir to the agent recursively at every boot, so the agent
|
||||
# already controls the legacy file.
|
||||
#
|
||||
# The unit runs as root because the file is root-owned `0600` where an operator
|
||||
# placed it. Root can still read the agent's `0400` store identity.
|
||||
|
|
|
|||
Loading…
Reference in a new issue