NEC-130: Editors cannot see collaborators' key fingerprints #194
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!194
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-130-editors-cannot-see-collaborators-key-fin"
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?
Task: NEC-130 — https://projectron.nerchure.com/tasks/130
The People dialog was offered only for folders this vault owns, so an editor could never see or compare a collaborator's key fingerprint. Comparing fingerprints is the defence against a server that substitutes keys (docs/security-model.md, CRYPTO-104), and it takes both people. Every member now reaches the dialog from the palette, the folder menu, the folder's settings page and the organisation's folder list. Editors see names, roles, fingerprints and Mark as compared; invite, role, remove, invitations and add-from-roster stay owner-only. The server already let any member list a folder's people, so only the plugin changes. Row logic moves to member-rows.ts with unit tests (mutation-checked both ways), and identity.test.ts gains an e2e step that opens the dialog as the editor vault and records a comparison.
Spec:
docs/changes/NEC-130-editor-people-view/spec.mdChangelog
Editors can now open a shared folder's People list to see and compare everyone's key fingerprints and mark them as compared.
bc14585aa1411ffd68ad