Bramble can now open a vault even when some entries cannot be decrypted, setting those entries aside in a quarantine store instead of refusing to open the vault.
- Incoming synced entries that do not decrypt under the vault's key are refused.
- A vault is synced only after it opens, and a vault that did not open is relocked.
- Unlock and decryption problems are shown as clear translated messages instead of raw crypto errors, and users are asked to report a vault that will not open.
- The extension keeps each sync session tied to the vault it started for.
All changes (10)
Features
- give each vault a quarantine store beside its file
- report undecryptable entries per entry in batch decrypt
Bug Fixes
- ask users to report a vault that won't open, linking the issue tracker
- harden the quarantine and keep unlock errors honest
- refuse incoming entries that don't decrypt under the vault's key
- show calm, translated copy instead of raw crypto errors
- sync a vault only once it has opened, and relock one that didn't
- set aside entries a vault can't decrypt instead of refusing to open
- pin each sync session to the vault it started for
Refactors
- keep the repository URL in one constant
Full Changelog: 1.28.0-firefox...1.29.0-firefox