aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 17:13:22 +0000
committertv <tv@krebsco.de>2026-11-16 18:28:47 +0100
commit4b28b1757a868b452d909d9283840092bfdb8479 (patch)
tree48b7524eda6d3ddd5ed069f53f2b5ab5943bd5ea
parentfa054999e84746d41561da4217ba84cd4d062d1a (diff)
federation: a signature's blob holds an empty reserved field
The design named the blob's hash and key, and said a signature is checked as continuum checks a user's, which takes `sha256` beside `sha512`, and any reserved field. Only the signer can vary that field, as it is signed, but one builder asked it empty and another didn't. It is empty, as `ssh-keygen` writes it, and the hash `sha512`, beyond what continuum's check asks.
-rw-r--r--docs/federation.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 750e0b0..a43dadc 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -125,9 +125,10 @@ Spread out:
(Changing the policy).
* **`sig`**: an SSH signature (`ssh-keygen -Y sign`, namespace `continuum-federation`)
over the event's bytes without `sig`: the SSHSIG blob of version 1, hashed with
- `sha512`, its key the event's `key`, in base64, padded and canonical, unarmored. It is
- checked as continuum checks a user's signature, strictly *(checked:
- `access::sshsig::verify_blob`)*.
+ `sha512`, its key the event's `key`, its reserved field empty, as `ssh-keygen` writes
+ it, in base64, padded and canonical, unarmored. It is checked as continuum checks a
+ user's signature, strictly *(checked: `access::sshsig::verify_blob`)*, which takes
+ `sha256` too, and any reserved field: the federation asks `sha512` and an empty one.
Three things no party signs, as their bytes need no signer, each without `party`, `key`
and `sig`: a version event (Changing the policy), and a federation's root and a fork's,