diff options
| author | tv <tv@krebsco.de> | 2026-11-09 04:46:19 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-09 05:48:17 +0100 |
| commit | 98a9180e39742725a61fb1966e342d7d212beee9 (patch) | |
| tree | cc4b8b5b8a1f022a00e5b46e2f849a3edc72301d /docs/openapi.yaml | |
| parent | 97a69e09021244e994602ac5038b4bd7bc16ba78 (diff) | |
access: what a node holds alone by `_continuum/local/<node ID>/<name>`
Setting a node's log filter took `write` on `_continuum`, all of the protocol data:
whoever could change one node's logging could change the swarm's members, remakes and
users too. Now what a node holds alone has paths of its own for capabilities, under
`_continuum/local/<node ID>/`: `log` (`/admin/log`), `config` (`/admin/config`) and
`debug` (`/debug`, always `write`), `read` to look and `write` to act
(`api::access::needed`, which takes the node's ID). So `_continuum/local/<node ID>` is
everything on one node, `_continuum/local/*/log` the log filter on every node, and
holders of `_continuum` keep it all.
Nothing is stored there: the store refuses writes under `_continuum/local`, and the
rules refuse a change touching it, as for epoch metadata. The quarantine stays with
`_continuum`: its entries are everyone's writes, which a node-local capability
mustn't show.
Diffstat (limited to 'docs/openapi.yaml')
| -rw-r--r-- | docs/openapi.yaml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/openapi.yaml b/docs/openapi.yaml index 8e6a688..0fad136 100644 --- a/docs/openapi.yaml +++ b/docs/openapi.yaml @@ -206,7 +206,7 @@ paths: '401': $ref: '#/components/responses/Unauthorized' '403': - description: The user may not write here (its capabilities, docs/access.md; in a swarm without a user registry, protocol data `_continuum` and the user isn't in `protocol-writers`), or epoch metadata or the swarm ID (`_continuum/epochs`, `_continuum/swarm`, never writable); a signed value not by this user, or whose signature doesn't check (the message says why). + description: The user may not write here (its capabilities, docs/access.md; in a swarm without a user registry, protocol data `_continuum` and the user isn't in `protocol-writers`), or epoch metadata, the swarm ID or what a node holds alone (`_continuum/epochs`, `_continuum/swarm`, `_continuum/local`, never writable); a signed value not by this user, or whose signature doesn't check (the message says why). '409': description: The path crosses an existing non-map value, or with `retype=false` the write would change a type (the message says where); a value not signed reaching one its user signs under a strict policy; a signed value where values aren't signed, or replacing another than the one there (read again); a value left not sealed as the swarm declares (`docs/access.md`, Values sealed for their readers). '415': @@ -330,7 +330,7 @@ paths: '401': $ref: '#/components/responses/Unauthorized' '403': - description: The user may not write here (its capabilities, docs/access.md; in a swarm without a user registry, protocol data `_continuum` and the user isn't in `protocol-writers`), or epoch metadata or the swarm ID (`_continuum/epochs`, `_continuum/swarm`, never writable). + description: The user may not write here (its capabilities, docs/access.md; in a swarm without a user registry, protocol data `_continuum` and the user isn't in `protocol-writers`), or epoch metadata, the swarm ID or what a node holds alone (`_continuum/epochs`, `_continuum/swarm`, `_continuum/local`, never writable). '404': description: No value at this path. '409': |