Ede_123

@steelej Your option 1 is basically what I'm doing, but any "off the shelf" sharing mechanism will be faced with file conflicts if the database is modified on different devices in parallel. Feel free to elaborate on how to resolve those conflicts easily... @Paul Thanks, triggers seem useful. I'll have a look at those. There is one for "Synchronized database file", so maybe I can copy the file manually after a sync to achieve binary identical copies locally and on the server. Syncing on save is not...

The issue at hand is really trivial: I have one database I have a copy on my local machine. I have a copy on my server. File systems on local machine and server are synchronized by a file-based synchronization utility. I usually access and modify the local copy for obvious reasons. However occasionally (e.g. when accessing the DB remotely from my mobile phone) I access and change the server copy directly. This is where it becomes inconvenient from a user-side: Local and server copies have diverged...

So this this mean the salt changes on every save? I really do understand how you might want to have different salts for different databases, but immediately after a sync it could absolutely be handled as the same database for al intents and purposes. I would be absolutely fine if my local database was simply copied to the server as-is after the sync.

Thanks Paul, this is the information I was looking for! So it is indeed as steelej suspected and the files will always differ. Is there a reason it is implemented like this (and is there a possibility to avoid it)? It would be great to have an option that ensures "sync" does not only sync entries, but also ensures the files are identical on a binary level.

I hope we can get some insight by Dominik on this, because he developed both components and has the necessary insight to explain what's going on. I'm sure he'll understand what the problem is and if this is an issue that I can solve on my end or whether it's an issue in KeePass.

Paul, I don't think you understand my issue. KeePass does not report anything at all (the status bar does reflect what it's doing, though: "Uploading file" , then "Downloading file", then the process is complete) - as far as KeePass is concerned I think the save succeeds. The problem is that the uploaded file does not match my local file after the synchronization on a binary level.

Paul, I don't think you understand my issue. KeePass does not report anything at all (the status bar does reflect what it's doing, though: "Uploading file" , then "Downloading file", then the process is complete - as far as KeePass is concerned I think the save succeeds. The problem is that the uploaded file does not match my local file after the synchronization on a binary level.

Yes, that's pretty much my current working thesis, but I don't enough of the internals of KeePass to verify it. I had hoped (and still hope) that someone on this forum has the necessary insight into the KeePass and IOProtocolExt code to explain what is happening here.