diff options
| author | tv <tv@krebsco.de> | 2026-11-18 11:13:12 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 12:21:27 +0100 |
| commit | cb9c78d0b76c401435aea781fc36845983c8f1f3 (patch) | |
| tree | 71baa306266a04b93fcae1c089425cf0c8d52035 /docs | |
| parent | fcd93f789b254d3e8a8f993d7fbc786f907abbc5 (diff) | |
federation.md, guides: a change taking what was refused keeps the number
A change that only has the federation take what it refused, reading
nothing it took otherwise, as ecdsa-sha2-nistp256 keys, keeps the
federation's number: it is rolled out to every node first, and used
after. A node that doesn't take it refuses what uses it, a version naming
such a key among them.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation.md | 7 | ||||
| -rw-r--r-- | docs/guides/federation/upgrades.md | 7 |
2 files changed, 14 insertions, 0 deletions
diff --git a/docs/federation.md b/docs/federation.md index f30cdd4..9659dbb 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -794,6 +794,13 @@ moves to it by a version of its policy that names it (`"federation": 2`), which parties pass once their nodes run a continuum that knows it. A node that doesn't know the federation, or a version, its swarm has stops taking events and says so. +A change that only has the federation take what it refused, and reads nothing it took +otherwise, keeps the number: the keys of type `ecdsa-sha2-nistp256` taken beside Ed25519 +ones are such a change. It is rolled out first and used after: every node runs a +continuum that takes it before any party uses it. A node that doesn't refuses what uses +it, a version naming such a key among them, and reads otherwise than the others until +it does. + ## The registry on it The krebs registry today: users, their hosts, the hosts' names, addresses and keys, as diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md index 945088d..95dab12 100644 --- a/docs/guides/federation/upgrades.md +++ b/docs/guides/federation/upgrades.md @@ -32,3 +32,10 @@ naming another is taken as a proposal, and a party's client backs none. A change to any of that is a federation of its own, with the next number, and its own design. A swarm moves to it by a version naming it, which the parties pass once their nodes run a continuum that knows it. + +A change that only has the federation take what it refused, and reads nothing it took +otherwise, keeps the number: `ecdsa-sha2-nistp256` keys beside Ed25519 ones. Roll it out +first, then use it: every party's operators upgrade their nodes, and only then does a +party name such a key in a version or a key set, or sign with one. A node not upgraded +refuses what uses it and reads otherwise than the others: a version naming such a key is +none to it, and it stays on the version before. |
