#241: outbound key gets its own row + fingerprint on the peering card (v0.6.25) #242
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/241-outbound-key-row"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #241.
The peer card now renders the outbound key (the one the peer issued us) symmetric with the inbound key:
Replacing the key now visibly changes the fingerprint — the state confirmation the bare #236 button lacked.
listPeersaddskeyFingerprint=peering.KeyIDOf(pr.Key)— the samesha256(pubkey)[:8]derivation as the inboundkey.id, so it leaks nothing and equals the fingerprint the peer shows as its inbound key id (two admins can verify the pair out of band). The raw key is still never echoed.peerCardElbelow the inbound row; the Replace-key affordance moves here from the actions row.peeringOutbound,peeringKeyUnknown.Runner: splice applied,
go vet/go build/go test ./internal/peering/... ./internal/api/...all green.