Which password manager to use?
-
I haven't seen it mentioned here so I'll throw it out there - 1Password. It's just a very smooth experience that I really appreciate.
-
I just don't want any unauthorized persons anywhere near my vaults in general. I also see my vault as a critical service that requires high availability, and I know enough about system administration to know that my network and I are not qualified to provide that.
-
Got a free family subscription through my work. Before that I was paying for it.
1Password is just great. Wonderful Linux support (desktop app, cli client, identity agent for SSH).
The major update to version 8 was rolled out to Linux first, actually.
One of the few pieces of software where you feel that the developers care about their product.
-
Actually keepassdx, and sounding syncthing
-
I like to use SyncThing for my keepass vault. Imo it's about as simple and elegant as it can get without involving third party services.
-
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.
-
Ignoring the security aspect of it Bitwarden is responsible for hosting a fault tolerant, highly available web app.
They have redundant networking, redundant servers, load balancers, redundant databases.
While you could host this yourself to these tolerances it's work and it's not free.
If you're using your password manager to the fullest you have a different password for every resource out there. It's more than a minor inconvenience if you get locked out of your passwords.
Their service is dirt cheap and it's absolutely worth every penny.
-
Vaultwarden is perfect imo
-
If you can't self host --> KeePass
If you can self host --> Vaultwarden -
I use KeepassXC on desktop, KeepassDX on my phone and keep it all synced with Syncthing. Works great
-
-
-
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.
-
Vaultwarden is not to be used in itself you can for example use the bitwarden app but with your vaultwarden server
-
Really I don't know, surely a bit less but in my opinion, not that much
-
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.
-
You're right. I was referring to the bitwarden app above. See https://github.com/bitwarden/desktop
It's an electron app, and there's no auto-update solution for DEB packages (ie no DEB repo for apt auto update).
Some people are probably happy with it, but I prefer KeepassXC which is more lightweight (ie not electron based) and can auto update via APT.
-
Hackers have increased their focus on cracking password managers by extracting data from RAM and registry, compromising local and cloud storage.
-
I'm not completely sure, but doesn't Bitwarden encrypt all data before it reaches the server? That means the server implementation is a bit less important. I guess you probably don't want to be leaking even encrypted databases though since there is a chance they could be cracked.
-
3rded moving from LastPass to Bitwarden and never looking back. I got out when LogMeIn got in.
