#vaultwarden — Public Fediverse posts

Daniel García released #Vaultwarden version 1.37.3. https://github.com/dani-garcia/vaultwarden

Daniel García released #Vaultwarden version 1.37.3. https://github.com/dani-garcia/vaultwarden

Daniel García released #Vaultwarden version 1.37.3. https://github.com/dani-garcia/vaultwarden

Daniel García released #Vaultwarden version 1.37.3. https://github.com/dani-garcia/vaultwarden

Daniel García released #Vaultwarden version 1.37.3. https://github.com/dani-garcia/vaultwarden

I gave vaultwarden a try last year when I was also playing with the idea of going from iOS to grapheneOS. But I didn’t switch and it languished stale on the hardware.

My question is this. Is the best path still to self host vaultwarden or switch to the official server?

#selfhost #1password #bitwarden #vaultwarden

Having now tried out both #Bitwarden and #Secrets (dot app), while neither is a perfect replacement for #1Password (because #Drop1Password) I think I am coming down on the side of Bitwarden for at least the short term.

Secrets' UX is a bit slicker…except for how its FF extension chose to do an extremely awkward dance with the GUI app instead of having something inline. Not a deal-breaker but a big red mark.

Secrets also lacks SSH key support; I /could/ go back to exporting privkeys to disk, but it'd be nice not to.

And the self-host potential of Bitwarden / #Vaultwarden is a compelling offramp in this "every company is a new opportunity to get rugpulled" world. Secrets is made by a small Apple-ecosystem design shop, who clearly do good work, but I'd be worried about a closure leaving the apps to eventually rot out of the App Store.

Want to move from #1Password to #Vaultwarden or #Bitwarden and wonder what works and what not? I did the move and created a small collection of scripts to ensure everything is transferred smoothly and in the structure I want: https://got.thinkberg.com/?action=summary&path=1pux-vaultwarden.git

Disclosure: I used #AI to help me with questions I had. I tested the script manually on the exported data in a secure environment w/o AI however, and it helped me to do the move much quicker. Check downloaded code!

Maybe just read the README and do it by hand, you won't fall for the pitfalls I went into when doing the simple path.

New #blog post: Migrating from #1Password to #VaultWarden

The recent news about @1password funding DHH hasn't sat well with me.

By luck, my annual renewal was only a few weeks away too.

So, I decided to change #passwordmanager

This post talks about how to set Vaultwarden up as well as how to migrate credentials across (the process is the same for #bitwarden)

https://www.bentasker.co.uk/posts/blog/general/migrating-from-1password-to-vaultwarden.html

#aliasvault sieht mit nach einem Upgrade zu #bitwarden / #vaultwarden aus. Das schaue ich mir die nächsten Tage mal an. Bisher lief mein Alias Management immer manuell und ziemlich umstänich ab über meinen Account bei meinem #mailcow Server.

@NebulaTide +1 for #keepass and sync (to a hosted #nextcloud in my case). Worked rock solid for more than 10 years for me. So just keep it simple is often a good advice. I thought about #bitwarden / #vaultwarden too, but I think for single user setup it isn't worth the effort...