Live sync SSH metadata in background
This commit is contained in:
parent
9887b47a40
commit
68153be5d5
9 changed files with 318 additions and 13 deletions
|
|
@ -138,7 +138,10 @@ bootstrap transfer path; future work will move provider/fetch behavior to
|
|||
at the peer. `geth ssh revocation sync <node-id>` requires
|
||||
`ssh_revocation.sync` on `resource:ssh:revocations`. Both commands merge
|
||||
authorized peer metadata into the local store for offline listing and later
|
||||
approval/signing workflows.
|
||||
approval/signing workflows. While the daemon is running, it also performs a
|
||||
background live-sync tick for known peers every 30 seconds. Live-sync stores
|
||||
per-peer high-water cursors in local metadata so repeated ticks request only
|
||||
newer SSH certificate-flow and revocation records.
|
||||
Importing or pinging a peer card never grants capabilities by itself.
|
||||
When `[iroh].local_discovery = true`, the daemon also advertises and discovers
|
||||
signed peer cards on LAN using a geth-specific mDNS TXT payload. That payload is
|
||||
|
|
|
|||
Loading…
Reference in a new issue