tweaks your troublesome Tux to make it tick smoothly
Q Secrecy without conflict
I use KeePass on my phone, laptop and desktop. I also use Syncthing to sync the database among the three devices.
Syncthing creates “conflict backup files” of the KeePass database when data is updated on more than one device. I’m looking for a solution, either a way for Syncthing to not generate these files or an alternative method of keeping the same password database on all devices. Is there a tool that will enable me to verify and combine both KeePass database files (since it’s encrypted)?
Jordan Welch
A We went through the same ourselves and tried several solutions. The problem with Syncthing is that it is, by its nature, non-interactive. When faced with a conflict it can’t ask what to do. It either makes a decision (possibly picking the wrong file), or saves both sets of data.
Our first approach was to store the database on , so each application was working with the same file. It doesn’t avoid the problem of two programs writing different versions of the same file, but with , that only means you may occasionally miss saving some data. Because is read a lot more often than written, this was a minor inconvenience. Even though the database file is encrypted, we weren’t comfortable leaving it () to give basically the same effect as using , but self-hosted.
