Open tipyn opened 10 years ago
raymontag
commented
10 years ago It means simply that anyone with the database credentials can edit the same database, not that you can login to different databases. However you could start two or more servers on different ports. Real multiuser and multidatabase support would be something cool for the future. It's not secured against race conditions yet.
tipyn
commented
10 years ago Thanks for your reply :)
What I mean is, with KeePass, you can have multiple users editing the same database (as you stated), but changes are not overwritten.
Taken from: http://keepass.info/help/v2/sync.html
In case of parallel updates and collisions, KeePass tries to store all information in an appropriate place. For example, when you have an entry E in a database A, make a copy B of A, change E in B, change E in A, and synchronize A and B, then E in A is treated as current and the changes made to E in B are stored as a history version of E (see tab 'History' in the entry dialog), i.e. the changes made in B aren't lost.
I’m basically just wondering if KeePassC has this capability, because currently my two co-workers use KeePass on Windows and Linux, and I have to use KeePassX on my Mac, which doesn’t support parallel updates, so whenever I need an entry adding or updating, I have to email one of my co-workers and they input the entry or change for me.
If KeePassC works then it means we can all use it! :)
Thanks, Luca
On 29 Aug 2014, at 15:45, Karsten-Kai König notifications@github.com wrote:
It means simply that anyone with the database credentials can edit the same database, not that you can login to different databases. However you could start two or more servers on different ports. Real multiuser and multidatabase support would be something cool for the future. It's not secured against race conditions yet.
— Reply to this email directly or view it on GitHub.
raymontag
commented
10 years ago I'm sorry to disappoint you but KeePassC hasn't these capabilities, yet :/ You have just one database opened, synchronizing two or some kind of version control isn't implemented. But it would be a cool feature. May be when I've finished my rewrite of the main client I could start to implement this.
tipyn
commented
10 years ago Ah ok, that really would be great as no other client actually has this capability - you can install KeePass on a Mac but it is not stable and crashes a lot - it’s a bit of a workaround rather than a proper solution. I will keep watching and hope you do implement it! I saw a post on the Arch Linux blog that discussed KeePassC and I was pretty excited about it - I work for an open source company and I know a lot of engineers that would jump at the chance to use a command line based password manager (in the same way they use IRSSI for Internet Relay Chat), so multiuser/database synchronisation would be fantastic.
Thanks! :)
On 29 Aug 2014, at 16:09, Karsten-Kai König notifications@github.com wrote:
I'm sorry to disappoint you but KeePassC hasn't these capabilities, yet :/ You have just one database opened, synchronizing two or some kind of version control isn't implemented. But it would be a cool feature. May be when I've finished my rewrite of the main client I could start to implement this.
— Reply to this email directly or view it on GitHub.
Hey,
We currently use KeePass at work, but I am using a Mac so I have to use KeePassX. The downside is that I cannot save any passwords in case I overwrite a change someone else is making. Synchronising is an issue. When it states "Network functionality including multiuser support", what does this mean? Does this mean lots of users can use the database without fear of overwriting other users changes?
Cheers! Luca