Reject conflicting SSH sync metadata

This commit is contained in:
Eric Wendland 2026-05-20 13:13:44 +02:00
commit 0e3ca7e80a
5 changed files with 159 additions and 16 deletions

View file

@ -200,8 +200,9 @@ Roadmap items should be actionable and checkable:
SSH certificate-flow metadata with `ssh_cert.sync` on `resource:ssh:certs` and
revocation metadata with `ssh_revocation.sync` on
`resource:ssh:revocations`. The daemon live-syncs known peers every 30
seconds using per-peer cursors; this is pull-only metadata sync, not yet a
CRDT/resource-log replication model.
seconds using per-peer cursors. Conflicting records with already-known ids are
rejected during sync import; this is pull-only metadata sync, not yet a
signed CRDT/resource-log replication model.
- cr-sqlite apply, iroh-docs, iroh-blobs provider/fetch, Automerge sync,
broader auth enforcement, and Keyhive/BeeKEM-style authorization are future
roadmap items unless implemented later.