We use this method in a team already since a year and I recommend everyone who is able to use this method to use it as it's easy to setup, very reliable and has great usability as changes are merged immediately.
It therefore only works properly though in local networks or anywhere where connectivity to the original kdbx file is stable, so that you can use a file system based access to the file. If the file is not accessible anymore on the other hand, KeePassXC will notify you. I think using KeePassXC on multiple devices accessing a single remote kdbx file works seamlessly as long as direct file system access to the actual and only kdbx file is used (such as an SMB share)! Changes done to the file while still open in KeePassXC can be automatically merged if configured. After analysing it for quiet some time now, let me use this comment to document it in detail and hopefully also motivate for a new feature of KeePassXC as I think it will affect many users out there.
After reading a lot of related issues, I think there is quiet some confusion in the acual issues and responsibilities related to cloud syncing in combination with KeePassXC, but I think this issue hits it best, so I am adding some details to it.
0 kommentar(er)
