Write a wrapper for KeePassX to open the old database if there is one but no new database
Start keepassx even if not doing a migration.
And simplify the conditions, it doesn't matter if Persistent folder is
mounted or not.
Move newly migrated keepassx database to the right place.
It's saved with a different filename by default, and not in the right
folder. This should solve this issue.
Save and restore keepassx settings around migrating the database.
Otherwise, in the same Tails session, if the user restarts keepassx,
she will be asked to open the old database first because of remainings
in the conf history. Let's clean that up.
KeePassX wrapper: forward the command-line args we got when we can (refs: #12369).
The .desktop file has "Exec=keepassx %f".
KeePassX wrapper: refactor (refs: #12369).
Let's not even go through the migration code if there's already a new-style DB.
KeePassX wrapper: avoid importing the v1 DB more than once (refs: #12369).
Without this change, after importing one's v1 DB, one would be prompted to
re-import it every time they start KeePassX again if they saved their new DB
under a name that's neither "New database.kdbx" nor "keepassx.kdbx".
KeePassX wrapper: document the (shared) purpose of two somewhat obscure lines of code (refs: #12369).
#5 Updated by bertagaz over 2 years ago
- Assignee changed from bertagaz to intrigeri
- QA Check set to Ready for QA
Branch is now (as of 2b21e99cbfbdeb7f6ec2a2a3f05f702d31e0ed63) confirmed to work as first planed.
This is good enough to set this ticket RfQA and for the branch to be merged.
Next step will require another ticket to track its progress. We decided to propose to move any uniq .kdbx file to the canonical name we support, and not care about people who store their database(s) outside this supported path.