How are you storing passwords and 2FA keys that proliferate across every conceivable online service these days?
What made you choose that solution and have you considered what would happen in life altering situations like, hardware failure, theft, fire, divorce, death?
If you’re using an online solution, has it been hacked and how did that impact you?
bitwarden/vaultwarden. currently the best experience for me. and youncan self host it
Seconded, plus hardware keys with passkeys disabled. Depending on your threat model, you might want your hardware keys to be a second factor, not a replacement for all the other factors. Passkeys do not fit into my threat model, as they are implemented as identity and password replacements rather than supplements
Bitwarden has an emergency contact who can access a vault after 2 weeks if you don’t deny it.
https://github.com/cyphar/paperback is great for a printed analog option as well. You could put your vault key into a multi paper printout, distributed amongst trusted people, so you need a quorum of them to get your secrets if you’re gone. Or get access to the family Google photos library, or whatever
BitWarden is really good. Has (nearly*) everything I want, works well across all platforms and the free plan is very featurefull. Even though I don’t really use any of the premium features, I still pay for the plan, to help fund development, it’s only 10€ a year.
- I say nearly because I’d love to have some form of autocomplete in Linux Wayland, outside of the browser extension. I believe one of KeePass apps does this (but only for X?)
You can kinda get autofill via a program called rofi-rbw on Wayland desktops (using wtype), but I found at least on Hyprland it often misses the field or the start of the password. I’d like to see a more consistent solution but definitely not via the official Electron app…
Another commenter said goldwarden implements that through the Remote Desktop XDG Portal, which only GNOME and KDE support at the moment (wlroots doesn’t implement it yet).
KeePassXC/DX + Syncthing
- Libre software
- No service as a software subtitute
- Decentralised
Theft/death - full disk encryption
Hardware fails/fire - decentralised
KeePass, and more specifically the KeePassXC (desktop) and KeePassDX (Android) ports.
My wife and I have shared a single KeePass database for about 15 years now and I couldn’t imagine switching to anything else.
My reasons have remained the same over the years:
- Free and open source
- Offline (but supports cloud sync)
- Lightweight
- Cross platform
- Supports autofill
I would never entrust the management of my credentials to a 3rd party online service. They’re an easy target (it’s only a matter of when, not if they are breached), and they could go out of business at any time.
We don’t use cloud storage for anything these days, but we keep the KP database (and many other things) synced across more than 7 devices using SyncThing, another amazing FOSS project.
Piggybacking on the comment. I also use syncthing to sync my keepass containers. Have you encountered duplication of database files (e.g. filename-sync-conflict-*), and if so, how have you solved them? I simply merge the files through KeepassXC when it happens.
That used to happen to us before we started using SyncThing (and before we had data plans on our phones).
By the time we migrated to it, we had a home server running 24/7 and this ensured that at least one device in the chain was always online, had the latest version of the database, and pushed it to other devices as they came online. Our phones also have data plans now, so things generally sync in realtime which helps avoid issues.
If you don’t have at least one always-online device, I think the next easiest way to avoid sync conflicts is to modify the database from one designated device. That way even if a conflict does arise, you’ll know which device is always correct.
For resolving the conflicts, I would open both databases, sort by modified, and review the latest changes in each.
I use KeePassXC. I have shared the keys with someone I trust in person in case of death. I sync by manually copying the database between my devices.
Bitwarden. I do like KeePass, but I am having problems with syncing it across devices. I know Syncthing exists but let’s say I add two passwords in two devices. Both of them don’t have the other one’s new password entry and that causes problems. Instead using online synchronization is much more convenient. Which is why I self host bitwarden.
