3 ms·
We use KeePass as a multi-user solution: the kdb file is on a network share (with relevant ACLs). The only thing you have to take into account is that you dont
by Ecio78 14y ago
We use KeePass as a multi-user solution: the kdb file is on a network share (with relevant ACLs). The only thing you have to take into account is that you dont have to leave it opened on your computer, so the typical use is: Open / Read (or Write) Password / Close it.
It works in small groups (we're three guys using it, two more frequently)
- estel 14y agoWe do something similar, but with relatively few users using Keepass 2, there aren't really any issues with leaving it open on multiple machines. Is there an issue besides synchronisation?
- Ecio78 14y agoafaik the second user should open it read only, so it cant update (that's why I was saying that the user should close it after having read/written some data)
- estel 14y agoThat was true for Keepass 1, but since 2 I think everyone can open it read/write? I think I'm prompted to "synchronise" when I save if another user has saved since I first opened it.
- tallanvor 14y agoAh, if KeePass v2 allows for synchronization, then that solves the big problem of people overwriting each other. Although I would probably still suggest a solution that allows more granular access controls and doesn't require everyone to share the same password for logging in.