swarm-bao: drop the default-policy grant; swarm/public/ is read by name
Writing bao's `default` policy needed a new stanza in the granter's own policy, which only the bootstrap token can upload, so deploying it took a manual root-token step. Nothing needed it: the one reader of the callout xkey's public half is `swarm-bao-nats-callout-xkey`, which logs in as the `swarm-nats-auth` role, and that role's policy already names the path. `swarm-bao-nats-auth-policy` writes that policy as the granter on every deploy, under the granter's existing `sys/policies/acl/swarm-*` grant. Removed: the `swarm-bao-public-read-policy` unit, its marker block, the granter's `sys/policies/acl/default` stanza, the granter-role restart of that unit, the bao.md section and the module-eval cases pinning them.
This commit is contained in:
parent
52c931c3a7
commit
06784e55fa
4 changed files with 31 additions and 224 deletions
|
|
@ -1,10 +1,10 @@
|
|||
//! The callout xkey: the curve keypair `nats-server` seals every auth request
|
||||
//! to, and that this responder seals every reply back with.
|
||||
//!
|
||||
//! Both halves live in the secret store. The seed is at [`SEED_PATH`], which
|
||||
//! only the `swarm-nats-auth` role reads. The public half is at
|
||||
//! [`PUBLIC_PATH`], under `swarm/public/`, which every token the store issues
|
||||
//! may read; the queue's host renders it into `auth_callout.xkey` from there.
|
||||
//! Both halves live in the secret store, and only the `swarm-nats-auth` role
|
||||
//! reads either. The seed is at [`SEED_PATH`]; the public half is at
|
||||
//! [`PUBLIC_PATH`], and the queue's host renders it into `auth_callout.xkey`
|
||||
//! from there.
|
||||
//!
|
||||
//! [`ensure`] creates the pair when the seed is absent and otherwise only
|
||||
//! reads it. [`load`] only ever reads, and is what the responder uses: a
|
||||
|
|
|
|||
Loading…
Reference in a new issue