From 6be5646df342b21fe82c63f59cfec5a369ab54f8 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 12:28:33 +0000 Subject: 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...`: 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. --- docs/access.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'docs/access.md') diff --git a/docs/access.md b/docs/access.md index c03f7c4..2f7fa5a 100644 --- a/docs/access.md +++ b/docs/access.md @@ -426,9 +426,15 @@ Signed then are what decides who may do what (every user's entry, every entry of `_continuum/access`, every ban), and the paths listed at `_continuum/access/userSigned`, a list of paths as capabilities name them, `*` for any one key: `[["config"], ["servers", "*", "secret"]]`. Each such value is an envelope, one string -(`cv1..`): the payload names the path, the value (`null`: deleted), -the user, when, and the envelope it replaces (`prev`), and the signature is the user's -over it, as `ssh-keygen -Y sign -n continuum-value` makes it, with one of its `keys`. +(`cv2...`): the value as its user wrote it (`null`: deleted); +apart from it, the meta, which names the swarm, the path, the user, when, the envelope +it replaces (`prev`) and its number (`seq`, one more than that one's, 0 where it +replaces none); and the user's signature over both, as +`ssh-keygen -Y sign -n continuum-value` makes it, with one of its `keys`. Where a place +holds several envelopes, written at once, the one with the highest `seq` is its value +(of equal ones, the one with the lower SHA-256), before anything that isn't one: so an +older envelope put back beside a newer one, by a change made not to see it, changes +nothing, whatever the order of the changes' operations. `scripts/continuum-signed` is a reference client, with `ssh-keygen`, `curl` and `jq`: it logs in by key, writes and deletes signed values (`put config '{"mode": "fast"}'`), and checks one against its user's keys (`verify config`). -- cgit v1.3.1