diff options
| author | tv <tv@krebsco.de> | 2026-11-07 22:35:21 +0100 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-07 22:35:21 +0100 |
| commit | 5471e5285e94ce7576e6c86f260fea15ed9503d1 (patch) | |
| tree | 310be18d26611d6aaf6d8b02a118ba2fb6ef4aa1 /docs/api.md | |
| parent | c3fde0fdd410902125f006f0a7d77ca030cb9061 (diff) | |
signatures: verified changes
GET /admin/changes shows whether a signature by its node vouches for
each change.
Auth plan M5.
Diffstat (limited to 'docs/api.md')
| -rw-r--r-- | docs/api.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/api.md b/docs/api.md index a02d3d5..89da7ba 100644 --- a/docs/api.md +++ b/docs/api.md @@ -237,7 +237,8 @@ signs it, so a member could name another. In a swarm without a registry, user na are each node's own (`--htpasswd`, or its proxy's): `alice` on two nodes is one person only where their operators make it so, which nothing checks. `GET /admin/changes` lists them, -newest first, with the paths each touched; `GET /admin/changes/settings` those that +newest first, with the paths each touched and whether a signature by its node vouches +for it (`verified`, Signed changes); `GET /admin/changes/settings` those that touched what is at `settings`. Every node holds every change, so user names are known to the whole swarm, and so is who wrote what, until a remake drops the history ([`remakes.md`](remakes.md)). |
