Self hosted open source simultaneous multiuser password safe with .deb or .rpm and an end user webui/android app
Self hosted open source simultaneous multiuser password safe with .deb or .rpm and an end user webui/android app
I'm looking into different self hosted open source multiuser password safes and while there are many options I haven't found one with a .deb or .rpm install - only a whole bunch of docker compose.
Do you know of any good options that are included in debian 12 or fedora 39 repositories or at least that has a .deb or .rpm?
Currently I'm using keepassxc but been asked for something that either has a webui login for end users or an android app.
edit 2024-02-17:
After looking into the .deb and .rpm options available (passbolt or unofficial vaultwarden-deb) I decided to bite the bullet and install a debian 12 vm that I will try out different docker solutions on.
You're viewing a single thread.
There are keepass android apps like KeePassDX. You can have server sync with WebDav, but I don't know about shared databases. Should work if you configure the WebDav server etc.
A friend of mine is a big fan of bitwarden but I have no Idea if that fits your requirement. Should have a webui tho.
The problem with the KeePass apps is that it works by syncing database files which means that there can be sync conflicts. Okay for me to handle, but not for the rest of my household.
I really want a server-client system where everyone works in the same database.Bitwarden is Docker, but also very well-liked. Might have to give up on the .deb / .rpm wish.
Thanks for the suggestion!KeepassXC implements a specific shared mode which is made to avoid conflicts.
I have no idea why no one uses it, I use it, works well.
This is the reason I don't use a shared database, I think that's what you're referencing?
Add ability to sync group structure with KeeShare - Status:Open
https://github.com/keepassxreboot/keepassxc/issues/3045KeyShare is, this issue is specifically about groups within KeyShare, you can create one KeyShare for each group if you require groups.
Would work if it was planned to be a system used by only techies or if we knew exactly what groups are wanted beforehand. Definitely gonna remember the tip, splitting it into several shared dbs didn't even hit me as an option.