Bramble now opens a vault even when some entries cannot be decrypted, setting those entries aside instead of refusing to open.
- Incoming entries that do not decrypt with the vault's key are refused during sync.
- A vault that fails to open will not sync and stays locked.
- Error messages are calmer, translated, and no longer show raw crypto errors.
- If a vault will not open, the app asks you to report it and links to the issue tracker.
- Sync sessions are tied to the vault they 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.31.0-chromium...1.32.0-chromium