[sakisv]

I only found out about Bitwarden a few weeks ago and it got me to change from KeepassXC and I'm overall very happy with the change.

The main selling points for me were that it's open source and they allow you to host it yourself.

Apart from these, I really enjoy the browser addons which don't require any jumping through hoops[1] and that they provide their own Android client and you don't have to play Play Store Columbus to find a decent one. It can also be used as an autofill service which allows it to interact with other apps which is incredibly useful.

But because nothing in this world is perfect, the downsides so far are:

1. Lack of shortcuts to copy only the username or only the password and forcing me to reach for the mouse. That's really annoying.

2. With KeepassXC you could have a keyfile that you was necessary to unlock your database while Bitwarden doesn't have that option. They do provide 2FA[2] but only TOTP and email for the free version (although $10/year for the premium subscription, arguably, is not much).

1: https://keepassxc.org/docs/keepassxc-browser-migration/ 2: https://help.bitwarden.com/article/setup-two-step-login/

[ekianjo]

> The main selling points for me were that it's open source and they allow you to host it yourself.

KeepassXC is open source too. And it does not require hosting. You can simply store your db onto a synced folder between devices and that's about the same anyway.

As for your comment regarding browser addons, I am not sure what "hoops" you are referring to. I installed the browser addons for KeePassXC and it took 5 minutes to setup and I have had no issue since. And the link you refer to is pretty self explanatory. Maybe Bitwarden makes that even more simple, but it's not that KeePassXC is utterly complex in the first place either.

On Android, KeePassDX is a good client that works with KeePassXC databases.

[sakisv]

You are right about the synced folder, and that's pretty much the approach that I was using. But I was keeping my DB in one provider and my keyfile in another, which means that I had to remember (or have otherwise access to) a total of 3 passwords to unlock my db. It worked, but when I recently had to change phones two times in a period of a few days it was increasingly annoying. Of course I could have kept my keyfile and the DB in the same provider, but still that's one password too many for me.

Thanks for the recommendation for KeePassDX, I will take a look.

[h1d]

> they allow you to host it yourself.

This is better than a hosted version in a way you don't reveal the URL of your login screen but yet letting anyone open up the entire vault with 1 password combination is a deal breaker for me.

Why don't online services provide unique URL for their logins for each users, so that no lucky breach happens?

(Like https://unique-id.service.domain)

I'd rather stick with an offline one.