Vaultwarden: Unofficial Bitwarden compatible server written in Rust • Hacker News Board

Re: Vaultwarden: Unofficial Bitwarden compatible server written in Rust

#121

Post by mbirth » Fri, Aug 16, 2024, 10:19 AM UTC

MrOwen wrote: post #101

kivle wrote: post #98

Earlier quoted context omitted.

I did too, and liked it until it taught me a valuable lesson about self hosting things. I started using the project while it was still called bitwarden-rs. Apparently they were told to rename by Bitwarden (understandable). My setup was based on their Docker images, and thinking it was the safest option I had set up Watchtower to automatically update to the latest image nightly to get the latest security patches. But…

I've seen watchtower burn so many people... Better to put everything in git and run your own renovate bot which will create PRs for you to review and also pull in the changelogs to the PR itself so you can check for breaking changes.

Just set Watchtower to quit after run and run it manually when convenient. This way, you’ll instantly know if some update went wrong and can fix it.

Re: Vaultwarden: Unofficial Bitwarden compatible server written in Rust

#122

Post by mbirth » Fri, Aug 16, 2024, 10:25 AM UTC

teekert wrote: post #61

darthrupert wrote: post #23

I have successfully used this for some time, but migrated away to just pass because synchronizing a pass "db" with syncthing tends to work much better.

I switched away from KeePassXC because I kept having sync issues with the DB :). Could have something to do with the way I work (always several PC on/active and my own NextCloud install with issues from time to time...). Vaultwarden never had any sync issues. I guess because changing one login will give you 2 versions of the entire database when a conflict occurs, for Vaultwarden, it's just that one credential, which…

KeepassXC can sync changes between your opened database and the (modified) file on your storage. However, you need to make sure your sync tool doesn’t see conflicts and renames the file, i.e. don’t save the database on multiple systems at nearly the same time.

Re: Vaultwarden: Unofficial Bitwarden compatible server written in Rust

#123

Post by mbirth » Fri, Aug 16, 2024, 10:33 AM UTC

einichi wrote: post #38

davidee wrote: post #26

After being fed up with AgileBits' (1P's owner) shenanigans (hiding critical threads on their user forum, ignoring customer voices wilfully, being generally dismissive of criticism), I decided to give Bitwarden a try. I used it in conjunction with Vaultwarden for a year with the idea that I'd evaluate it as a family-wide replacement for 1P. In the end I went back to 1P. 1P does some things amazingly well. Here's the…

I actually swapped over from 1P to Bitwarden because the experience on Mac just got worse and worse over time, bloated and buggy. Bitwarden isn't rapid, but at the time it was, to my surprise, a better experience than 1P, at least on MacOS.

I’ve switched from 1P to Strongbox which is using a Keepass2-compatible database in the background. But Strongbox integrates into the Apple AutoFill API so it works (and mostly feels) like the native Apple Keychain thing. Only for Chrome or Firefox you’ll need a plugin and then it works similar to Bitwarden. But I don’t use these.

Re: Vaultwarden: Unofficial Bitwarden compatible server written in Rust

#124

Post by teekert » Fri, Aug 16, 2024, 11:09 AM UTC

mbirth wrote: post #122

teekert wrote: post #61

Earlier quoted context omitted.

I switched away from KeePassXC because I kept having sync issues with the DB :). Could have something to do with the way I work (always several PC on/active and my own NextCloud install with issues from time to time...). Vaultwarden never had any sync issues. I guess because changing one login will give you 2 versions of the entire database when a conflict occurs, for Vaultwarden, it's just that one credential, which…

KeepassXC can sync changes between your opened database and the (modified) file on your storage. However, you need to make sure your sync tool doesn’t see conflicts and renames the file, i.e. don’t save the database on multiple systems at nearly the same time.

Oh that is nice, but NextCloud never made effective use of that. It's been a while but I also found the browser plugins and methods to use the DB on mobile platforms cumbersome. Idk, perhaps much has changed, I have been on Vaultwarden for years now, and more recently switched to Proton Pass. Both have excellent Web UIs, iOS/Android apps and browser plugins.

Moreover, Vaultwarden and Proton Pass make using Passkeys and sharing credentials with org or family members trivial (arguably Proton Pass even more so than Vaultwarden).