3 ms·
Word of warning: Don't use KeePassXC when your co-workers use KeePass2 using a network drive. KeePassXC doesn't support KP2's sync protocol. You'll clobber othe
by Sander_Marechal 6y ago
Word of warning: Don't use KeePassXC when your co-workers use KeePass2 using a network drive. KeePassXC doesn't support KP2's sync protocol. You'll clobber other people's changes when you save using XC. It took us a few weeks before we noticed that many passwords were missing.
- Florin_Andrei 6y agoBut that sounds like the wrong thing to do. Why are you all pointing all your apps at a shared "database" file? And how about locking issues?
- SloopJon 6y agoThis seems to be a supported feature of KeePass 2: "When invoking the 'Save' command, KeePass checks whether the file on disk/server has been modified while you were editing it. If it has been modified, KeePass prompts whether you want to overwrite or synchronize with the file." https://keepass.info/help/v2/sync.html https://keepass.info/help/v2/sync.html KeePassXC, on the other hand, does not seem to have been designed for shared synchronization: "Cloud synchronization ... can be easily accomplished by simply storing your KeePassXC database inside your shared cloud folder and letting your desktop synchronization client do the rest. We prefer this approach, because it is simple, not tied to a specific cloud provider and keeps the complexity of our code low." https://keepassxc.org/docs/#faq-cloudsync https://keepassxc.org/docs/#faq-cloudsync
- quicksilver03 6y agoThe synchronization feature is what's keeping me on KeePass 2 (running on Mono in Linux) , despite the fact that the interface looks completely out of place in my KDE system.
- NoSubstitute 6y agoOh, thank you! Potentially saved us from unnecessary headaches. I'll be sure to use regular KeePass when editing a shared database. For my own db I prefer KeePassXC, and use DropBox for syncing between devices.