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.
Hackers have increased their focus on cracking password managers by extracting data from RAM and registry, compromising local and cloud storage. 25% is a threefold increase compared to the previous year's figures.
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.
I hear good thing about Vaultwarden, but the web UI is horrible.
Vaultwarden's web UI is very confusing, especially the search feature. And it's difficult to move items between folders/collection. The desktop app is available as DEB/RPM package but without auto-update, which isn't great.
Fon now I'm sticking to KeepassXC because the desktop app for my Linux distribution has a package for it and allows auto-update. The UI works well, and it has decent browser integration. Syncing isn't smooth, but I can live with this.
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.
I know you're asking for an integrated sync but this has been flawless for me and only rarely notice a delay between machines including android, linux, and windows (less that 30s in any case)
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.
VW isn’t the self hostable version of BW. It’s a complete rewrite. I don’t know if it is audited in the same way as BW, so I wouldn’t recommend it until you check that. BW can be self hosted as it is. VW is a rewrite with all the premium features unlocked for free
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.
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.
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.
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.
I also use Unix pass and self host a git repo over Tailscale to keep it synced across devices. Works like a charm so long as I remember to push whenever I edit a password somewhere.
Keepass2android should be able to handle nextcloud sync from within the app so that might work better than on device sync. If your done with keepass bitwarden or proton pass are common alternatives
I do the exact same thing as OP with KeepassDX at work and works pretty nice so far, since I gave KeepassDX the right acces rights on the nextxloud directory.
What diferences have you figured out so far with Keepass2android in comparison ?