That gets the job done but I'd better remember to do that from time to time.Īm I missing something, or does that about sum it up? In other words, KeePassXC alone doesn't do a complete backup job.
Of course there is the manual approach of clicking Database on the toolbar, followed by "Save Database Backup.", and specify a different location and name for the backup file.
It does not offer an option to specify a different target location. "It is a good practice to create copies of your database file and store the copies of your database on a different computer, smart phone, or cloud storage space such a Google Drive or Microsoft OneDrive." No argument there.Īfter turning on the "Backup database file before saving" option in the General Settings area, all that does is create another copy of the database with "old" appended to the database name, in the same location/folder where the main database is. And the most puzzling of all is I still get the perm denied error in screenshot 2.Basic backup principles say it's wise to always backup your data to a totally different location. Just for good measure, both accounts individually too.
Google Sync was reporting a failure to sync too, so I decided to override ownership.īoth my user profiles are Administrators, so I added the Administrator group to have full access to the database file. I thought maybe some other program is locking it from being edited (although I would assume read access is still available?). You may be able to compile KeePassXC for the mobile OS of your choice, but it isnt at all optimized for mobile screen sizes and form factors, let alone multi-touch input. I tried to manually re-open the database, and I get a perm error (screenshot 2). For KeePassXC, porting it properly to mobile platforms would require a full rewrite. Went back to work user, still same issue. I checked to see if the database was open on my play user, and it was, so I closed it. Encrypt my passphrase with my public key, and take its hexdump. Encrypt my keyfile with my public key, and take its hexdump. The DB is encrypted with a high-entropy (> 120b) passphrase.
Suddenly today, I switched over to my work user and tried to open my database, and I can't (see screenshot 1 above). KeePassXC Secure Backup Here's the plan: Upload the password DB to a private Github repo. I've been using KeepassXC for about a week, and I'm starting to get used to it. I also switch between two different window users for work + play. So I've been using Google's "Backup + Sync from Google", which works fine. Totally fine with using other programs to sync. Still, I think it can be an option, but I can live with it.
I also really loved Google Drive sync for databases, and I understand KeepassXC's reasoning of why it's not natively supported in the program.
In KeepassXC, some shortcut keys are gone, I can live with that.
Perplexingly, it seems that Windows is not providing permissions for KeepassXC to open the database.