this post was submitted on 12 May 2024
1043 points (98.2% liked)

Open Source

30988 readers
425 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 3 points 5 months ago (1 children)

I have a lot of experience with both. As a tech savvy user, I slightly prefer KeePass. Syncing between devices is slightly more painful, but I find it to be more reliable, and it doesn't have the attack surface that Bitwarden does. (While encrypted, Bitwarden still really wants a web server and a local database connection.)

VaultWarden is probably better for those who can't be bothered to move a file around and want direct browser integration. With KeePass when you need a password, you'll make sure the username has focus and then alt+tab to KeePass and hit "autofill". Some sites won't take "username{tab}password{enter}" and you'll have to customize the configuration.

VaultWarden is better at prompting you to add new passwords. I prefer the workflow that's encouraged by KeePass, where you open the app first and use the app to open the URL. (You can do this in VaultWarden too, but it's less obvious.)

[โ€“] [email protected] 1 points 5 months ago* (last edited 5 months ago)

On my case i use Syncthing-fork to have my database synchronized on my tablet and phone, you'll be surprised how easy to use is, and doesn't require a server ๐Ÿ˜„