#241: outbound key gets its own row + fingerprint on the peering card (v0.6.25) #242

Merged
Cordy merged 2 commits from feat/241-outbound-key-row into main 2026-08-15 14:56:11 +00:00
Owner

Closes #241.

The peer card now renders the outbound key (the one the peer issued us) symmetric with the inbound key:

INBOUND KEY   3fd2ac2451e1…   [Revoke]
OUTBOUND KEY  da2ed8d3fb77…   [Replace key]

Replacing the key now visibly changes the fingerprint — the state confirmation the bare #236 button lacked.

  • Backend: listPeers adds keyFingerprint = peering.KeyIDOf(pr.Key) — the same sha256(pubkey)[:8] derivation as the inbound key.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.
  • Frontend: new OUTBOUND KEY row in peerCardEl below the inbound row; the Replace-key affordance moves here from the actions row.
  • i18n: peeringOutbound, peeringKeyUnknown.

Runner: splice applied, go vet / go build / go test ./internal/peering/... ./internal/api/... all green.

Closes #241. The peer card now renders the outbound key (the one the peer issued us) symmetric with the inbound key: ``` INBOUND KEY 3fd2ac2451e1… [Revoke] OUTBOUND KEY da2ed8d3fb77… [Replace key] ``` Replacing the key now visibly changes the fingerprint — the state confirmation the bare #236 button lacked. - **Backend**: `listPeers` adds `keyFingerprint` = `peering.KeyIDOf(pr.Key)` — the same `sha256(pubkey)[:8]` derivation as the inbound `key.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. - **Frontend**: new OUTBOUND KEY row in `peerCardEl` below the inbound row; the Replace-key affordance moves here from the actions row. - i18n: `peeringOutbound`, `peeringKeyUnknown`. Runner: splice applied, `go vet` / `go build` / `go test ./internal/peering/... ./internal/api/...` all green.
Cordy merged commit 24f482bf8a into main 2026-08-15 14:56:11 +00:00
Cordy deleted branch feat/241-outbound-key-row 2026-08-15 14:56:14 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#242
No description provided.