keepass-diff VS git-credential-keepassxc

The sync conflicts happened to me whenever I left keepass databases open and changed it on multiple devices. Usually, those changes were adding new accounts into the databases or changing a password on one while adding something on the other. This regularly happened when working in a team.

I assumed people would switch from Keepass + database synced on a private server to something else when they started working in teams and need better/easier permission models. :)

As you have mentioned it, I have written the tool keepass-diff (<https://github.com/Narigo/keepass-diff/>) to help me for exactly these conflicts and I could quickly resolve the issues with it. It was still useful enough to let me keep using Keepass. Was it not working for you or was it too hard to use because of how it needs to be set up first? Would you have stayed with Keepass + sync if something similar to this was integrated into UI clients?

I had this problem as well, these conflicts may happen when you keep Keepass clients open and add passwords on two different machines.

I have written a CLI tool in Rust called keepass-diff that may help you with this: https://github.com/Narigo/keepass-diff

The keepassxc CLI reopens the database separately; it's actually possible to use git-credential-keepassxc† to do the scripting instead because it acts more like a browser (so it interacts with the already running instance of KeepassXC).

† https://github.com/frederick888/git-credential-keepassxc

I use KeepassXC password manager[1], it keeps my TOTP information and makes it available to use on all my devices. It syncs between my devices using Dropbox. Kepassium[2] makes it available on iOS, and Keepass2Android[3] makes it available on Android. It also manages my SSH keys and adds them to the ssh-agent, even on Windows. and houses a backup of my GPG keys. I even found that it can manage my credentials for use in scripts and git using git-credential-keepassxc[4].

Similar functionality can be had from 1Password[5], of you're into the more fancy experience. As a bonus this approach makes it very easy to store all those backup codes that dotp services often give you. Won't help your current predicament but will prevent it from happening again :)

1: https://keepassxc.org/

2: https://keepassium.com/

3: https://github.com/PhilippC/keepass2android

4: https://github.com/Frederick888/git-credential-keepassxc

5: https://1password.com/

I have https://github.com/Frederick888/git-credential-keepassxc which can probably make things easier...