They have totally different design goals which is why Bitwarden is more resource-hungry and more complex to deploy. Bitwarden can scale up to large use cases such as companies with hundreds of thousands of employees (it's what they run on the hosted version, after all), whereas Vaultwarden is designed to be small and light for home use cases where you almost always have <10 users total.
I found keepassium for the work phone and I was in love that I could keep a separate db with my OTPs under a password and backed up.
Then I left that job and had to split my OTPs. Vanilla keepass for droid will gives me the OTP values for gitlab etc, so it's good there, but Vanilla keepassium for Android has no camera/QR->OTP input that I have yet, one that works like keepassium does and is all compatible down the line. I'd love to keep using it to maintain the existing separate keepass OTP db I have.
Do you (or anyone) know of a good combo for droid that gets
keepass
backup to box/gdoc/etc
qr for OTP
In one final package? Does XC do it in a way we think may be compatible?
Keepass2Android does all that on android. It natively supports Dropbox, google drive, one drive, nextcloud, pcloud, and mega, plus you can use WebDAV or sftp. When editing an entry, the totp setup has the ability to scan qr codes with the camera. Plus, the whole thing is free and open source.
They even have a package on F-Droid, though that build lacks the built-in support for cloud syncing (due to F-Droid restrictions prohibiting binaries, I think).
I've used this app for years on android, paired with various cloud sync options as providers change their restrictions and capabilities. On desktop, I use keepassxc.
Hm i switched from KeePass to Bitwarden because the latter lets me use my passwords on multiple devices and as a Firefox extension that enters my credentials at a shortcut.
Can you elaborate why you think KeePass is better?
It's very useful if you don't use a password manager and/or reuse passwords.
The most useful part about it to me is the API. You can tie it in to Active Directory to blacklist all hashes that appear in any breach, plus expire/force a password change if any user on your domain uses a password that has been in a breach. It completely eliminates that vector from threat actors immediately.
The most useful part about it to me is the API. You can tie it in to Active Directory
This trick alone makes my Lemmy addiction pay off. Thanks for even suggesting such magic is possible. Adding that as a task after my samba-AD rebuild this very f'n week.