You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix Zero-Knowledge vaults: set the passphrase at creation + verify on unlock
You could create a ZK space but were never asked to *set* a passphrase: the first
thing typed on entry silently became the key, with no confirmation and no wrong-
passphrase check — a typo encrypted files under a passphrase you couldn't reproduce
('Déchiffrement impossible'). The crypto was correct; the flow wasn't.
- Creating a secured space now prompts for the passphrase twice (confirmation).
- A per-vault 'verifier' (a constant encrypted with the vault key) is stored so
unlocking can detect a wrong passphrase immediately, and a stale cached key is
rejected instead of trusted. Legacy vaults (no verifier) behave as before.
- Client now generates the per-vault salt so it can derive the key before the
round-trip; server falls back to its own salt if absent.
- Schema: Folder.zkVerifier (+ migration); shared create schema accepts zkSalt /
zkVerifier; serializer/types expose zkVerifier.
- Also bump the GitHub update-check timeout to 12s.
41 tests pass.
0 commit comments