Which password manager to use?
from vaionko@sopuli.xyz to privacy@lemmy.ml on 11 Feb 2025 08:43
https://sopuli.xyz/post/22497771

I currently use KeepassXC that is synced through NextCloud. The sync isn’t very elegant, especially on my phone. So I’m looking for a new password manager, which has a native server sync support that I can self host. What do y’all recommend? I need at least a phone app and a browser integration that can autofill.

#privacy

threaded - newest

EmbarrassedDrum@lemmy.dbzer0.com on 11 Feb 2025 11:17 collapse

Bitwarden.

My recommendation: Don’t use Vaultwarden (self hostable server side of bitwarden. Really easy to run and use). Why? You’re not a security personal, and securing your vault isn’t your job. You might do a slight mistake that’ll lead to the compromise of your vault.

The people at Bitwarden have their work dedicated to securing the vaults and all they do is security. And they’ll probably do it better then you. When it comes to serious matter, I prefer to trust the professionals.

superglue@lemmy.dbzer0.com on 11 Feb 2025 23:27 next collapse

Just to play devils advocate. Bitwarden.com is a much more valuable target. My instance is behind a VPN. I think its actually far more likely Bitwarden will have a breach similar to LastPass then I will. But I agree with you mostly.

asap@lemmy.world on 12 Feb 2025 11:00 collapse

The data stored on Bitwarden’s servers is completely encrypted though, which means a breach will not yield useful data, unlike the plain text storage for LastPass.

I have the ability to selfhost BW so I am interested in counterpoints.

superglue@lemmy.dbzer0.com on 12 Feb 2025 15:01 collapse

Yes I agree. I was just offering a counter to the statement that Vaultwarden isnt as safe as Bitwarden. They both are encrypted but my vaultwarden instance is a lot less likely to experience a breach than Bitwarden. The guys with real skill are going after Bitwarden not me.

EmbarrassedDrum@lemmy.dbzer0.com on 20 Feb 14:11 collapse

That’s a good point.

Notice, your server is less likely to be targeted. But much more likely to receive a breach once it’s targeted.

It’s helpful to analog. You got gold. Thieves are more likely to target a bank, but if they’ll know of some gold in your house, it’ll be much easier for them to take it from your house rather than from the bank.

And now you have to work and make sure people don’t find out about the gold in your house. Because once they did it’s game over.

EpicGamer@lemmy.world on 11 Feb 2025 12:09 collapse

Doesn’t the server just hold an encrypted vault? What could go wrong when the server is compromised? Just thinking out loud I don’t know the answer

EmbarrassedDrum@lemmy.dbzer0.com on 20 Feb 14:19 collapse

Let’s say I have an unupdated patch and my server is now vulnerable.

This could really happen. I have work and life to worry about and I might not notice.

This vulnerability, could be in the BW instance itself (say the web server or the backend itself), or in the server itself (say an old OpenSSH version), or another service (NextCloud instance hosted in the same server under a different subdomain).

So, first we see it’s a big attack surface. In any of those entrances an attacker could gain access to my server and with it the vault. It’s a short way from there to install a keylogger on the website where BW is hosted, and get my master password ¯_(ツ)_/¯.

Now take into consideration that I just sat a couple of minutes to think about this, and I’m not a professional in cyber security or web security. Neither blue nor red team. A professional, with more knowledge, time, experience and resources, could probably bring up much more things.

EpicGamer@lemmy.world on 27 Feb 18:54 collapse

I would just put a server on the internet with only the bitwarden ports open to the internet. And put the server in its own isolated environment. With automatic updates I would be comfortable with this. Even if for any reason the isolated server gets compromised, the server is mostly a glorified sync server.