Credential-derived key custody — spike (local/LDAP only) #30
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Manuel's
passwordHash + user-PIN → keymodel: derive the encryption key from user credentials so it lives only in RAM (zeroed after use) and the backend holds no standing key — a stronger data-processor posture.Hard constraint (the crux): this works only where the server sees the password —
It's the E2E trade-off relocated to key derivation: "server never holds a usable key" XOR "transparent decryption for all clients." OpenBao does not solve this (orthogonal). Spike in local/LDAP mode, measure the UX/threat trade honestly, write it into
ENCRYPTION-COMPARISON.md. This is the risky half of the weekend prototype.