pull swarm closures through the nix daemon: substituters in the fragment, merged root-only netrc
This commit is contained in:
parent
63ae5d6cbf
commit
ef68baa00f
1 changed files with 582 additions and 382 deletions
|
|
@ -56,12 +56,12 @@ next start.
|
|||
|
||||
`none` cuts the daemon only. It leaves the agent's egress alone.
|
||||
|
||||
Under `host` an agent shares the daemon with the hive's own closure pull, and
|
||||
gains nothing from it. The daemon trusts the swarm cache's public key, but it
|
||||
has no cache address and no pull token (hive-c0re fetches with a netrc readable
|
||||
only by `hive-core`), so an agent can't fetch from the private cache. It can
|
||||
still ask the daemon to substitute from the public caches the host configures, as
|
||||
before. See
|
||||
Under `host` an agent shares the daemon with the hive's own closure pull. The
|
||||
daemon holds the swarm cache as a substituter, with the pull token in a netrc
|
||||
only root reads, so an agent can ask it to substitute a swarm closure as well as
|
||||
a path from the public caches the host configures. The agent never sees the
|
||||
token, and a closure is world-readable once it's on the host and holds no
|
||||
secret. See
|
||||
[hive-c0re-privilege.md](hive-c0re-privilege.md#closures-from-the-swarm-cache).
|
||||
|
||||
## Threat model
|
||||
|
|
|
|||
Loading…
Reference in a new issue