diff options
| author | tv <tv@krebsco.de> | 2026-11-15 12:28:33 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 12:28:33 +0000 |
| commit | 6be5646df342b21fe82c63f59cfec5a369ab54f8 (patch) | |
| tree | 48ede9923ab4fa762623a6e32b9b18a088276b98 /docs/openapi.yaml | |
| parent | d1d081cf8e0e8bb5809c1c82bbdfec6bd7ad0285 (diff) | |
signed values: value and meta apart, numbered; the highest seq is read
A member could put a user's older signed value back beside a newer
one: a change made with dependencies from before both is judged where
the place was empty, so the older envelope (`prev` empty) is taken;
and of values written at once, the one read was the one with the
highest operation, which whoever writes the change steers. A revoked
capability, a lifted ban or an earlier policy came back that way,
signed by whoever signed it then.
An envelope is now `cv2.<value>.<meta>.<signature>`: the value as its
user wrote it, and apart from it what continuum adds (swarm, path,
user, at, seq, prev), the signature over the value's line and the
meta's. `seq` is one more than that of the envelope it replaces, 0
where it replaces none; every node checks it with `prev`.
Of the values a place holds, written at once, signed ones are read
before any other, the highest `seq` first, of equal ones the lower
digest (`store::candidates`): reads, snapshots and writes all go by
it. An older envelope beside a newer one changes nothing.
`application/continuum-signed` is the value's line, the meta's, then
the signature; `scripts/continuum-signed` writes and checks it so.
The wire version goes up: nodes must agree on what a place's value is.
Diffstat (limited to 'docs/openapi.yaml')
| -rw-r--r-- | docs/openapi.yaml | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/openapi.yaml b/docs/openapi.yaml index 1b4a199..5728da5 100644 --- a/docs/openapi.yaml +++ b/docs/openapi.yaml @@ -110,7 +110,7 @@ paths: - $ref: '#/components/parameters/at' - name: raw in: query - description: Values their users signed as stored, as envelopes (`cv1.<payload>.<signature>`), to check them. + description: Values their users signed as stored, as envelopes (`cv2.<value>.<meta>.<signature>`), to check them. schema: type: boolean default: false @@ -158,8 +158,8 @@ paths: `application/vnd.continuum.timestamp; format=rfc3339|unix|unix-ms|http-date`; a body that isn't one is `400`, saying why. - A value its user signed (`application/continuum-signed`: the payload's line of - JSON, then its armored SSH signature; `api.md`, Signed values) is written as its + A value its user signed (`application/continuum-signed`: the value's line of + JSON, the meta's, then the armored SSH signature of both; `api.md`, Signed values) is written as its envelope where values are signed: by the authenticated user, for this path, with one of its keys, replacing what is there. A signed `null` deletes (`204`). parameters: @@ -192,7 +192,8 @@ paths: schema: type: string example: | - {"swarm":"6f9a…","path":["config"],"value":{"mode":"fast"},"user":"alice","at":1762400000000,"prev":""} + {"mode":"fast"} + {"swarm":"6f9a…","path":["config"],"user":"alice","at":1762400000000,"seq":0,"prev":""} -----BEGIN SSH SIGNATURE----- U1NIU0lH… -----END SSH SIGNATURE----- |
