home.social

#vaultwarden — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #vaultwarden, aggregated by home.social.

  1. 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

  2. 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.

  3. #til Der Umzug von #1password zu #vaultwarden ist deutlich einfacher als gedacht und in wenigen Sekunden erledigt. Interessanterweise nur unter iOS (Android kann ich nicht prüfen). zenzes.me/til-passkeys-ziehen-

  4. @depone hier wird #vaultwarden in einem docker Container selbst gehostet. Bin damit recht glücklich.

  5. Bisher klappt der Umstieg von #1Password auf #Vaultwarden ganz gut. Was nervig ist, ist die Migration der Passkeys. Da werde ich noch auf Nitrokey umsteigen.

  6. 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: got.thinkberg.com/?action=summ

    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.

  7. So, mal #Vaultwarden auf das heimische Blech gepackt um ganz vielleicht #1Password mal abzulösen. Der @thinkberg hat gesagt das ist OK.

  8. 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)

    bentasker.co.uk/posts/blog/gen

  9. If you're wanting to self-host a password manager you might want to check out Vaultwarden. It's a free open source alternative to 1Password, Bitwarden etc. It is compatible with Bitwarden clients but is a totally separate project. More info at:

    🌱 github.com/dani-garcia/vaultwa

    It's available to self-host through @yunohost at apps.yunohost.org/app/vaultwar or by installing manually using the instructions at github.com/dani-garcia/vaultwa

    #SelfHosting #Vaultwarden #1Password #Bitwarden #Alternatives #FOSS

  10. @docyeet Indeed. It’s on my list to check out other potential clients for #VaultWarden just in case that does become a thing. Star Trek made it clear, triple redundancy on all key systems! I’m only at single failover on a few.

  11. Younger Rob would have quietly smug after the recent #1Password drama given I moved to #VaultWarden a few years ago. But if the last 10 years have taught us anything is that #Enshittification is an equal opportunity employer and will happily onboard any and all products. I now keep fingers permanently crossed that the various products I use, including #SelfHosted ones don’t succumb to the seemingly irresistible lure.

  12. I quit #1Password when they went to cloud-only syncing, and I can recommend #Vaultwarden as being fairly easy to set up on a #RaspberryPi at home: github.com/dani-garcia/vaultwa

  13. Well, I was already on the fence about Proton, and kept it because #protonpass is solid and I didn't have a push to change.

    Today, my proton pass chrome extension blocked me from viewing a password by overlaying an ad for their "ultimate" bundle.

    No. Fuck you. I am paying you, @protonprivacy, because I don't want an ad-laden product.

    Will be moving to a self-hosted #vaultwarden and #simplelogin tonight and cancelling my proton account.  Zero tolerance for this.

  14. @stodarahodan May I interest you in our Lord and Savior: a self-hosted #vaultwarden instance? :D

  15. Apropos the latest 1Password and Debian debacles:

    I'm running Vaultwarden and Caddy under Alpine Linux on a Raspberry Pi 5. Memory usage is 200 MB. Connections from outside my network through WireGuard on the router.

    #Vaultwarden #AlpineLinux #RaspberryPi #SelfHosting

  16. @weavejester

    Good decision — at least from my point of view. If you’re switching anyway, you might as well self-host #Vaultwarden: Bitwarden-compatible, lightweight, and under your own control.

    #Bitwarden #Vaultwarden #SelfHosting

  17. Anyone have success in exporting their @1password vault on the Linux desktop app?

    Nothing happening when I try to export.
    Finally doing the full migration to Vaultwarden after their latest support fro racism.
    #vaultwarden #SelfHost

  18. @josh #VaultWarden is probably the closest to the 1Password experience. Not sure about AI though.

    Thanks for the heads-up - all of this Omarchy nonsense is certainly revealing. As one of my favourite sayings goes, "If someone shows you who they are, believe them."

  19. #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.

  20. Meine aktuelle private #QNAP #NAS Baustelle:

    #SSLVPN (TCP 443) mit #OpenVPN (#QVPN App)
    • Interne CA für .internal (#OpenSSL)
    #PiHole (Docker) für .internal DNS A Records
    • Reverse-Proxy #Caddy (Docker) für HTTPS
    #Vaultwarden (Docker)
    #FreshRSS (Docker)

    Für den sehr sporadischen Dateizugriff verwende ich die Qfile-App.

    Nur das SSL-VPN ist aus dem Internet erreichbar.

    Weitere #Docker Ideen:
    • Nextcloud (wenn Qfile nicht ausreicht)
    • Paperless NGX

    #opensource #privatecloud #cloud

  21. @Larvitz @jwildeboer I just re-tooled the Ansible for my "private cloud" to use the Traefik configuration from that blog post and tested it on a VM at Hetzner. 20 minutes to a private cloud with the following components:

    - #Keycloak
    - #OneDev
    - #Vaultwarden
    - #Nextcloud AIO
    - #SearXNG
    - Static blog site using #VitePress
    - #OpenVPN

    I also have a playbook to automate the backups (on and off-site)

  22. ... ich hab mir jetzt #Vaultwarden auf den Server hier zu Hause installiert (mit #Reverseproxy auf'm root und #autossh zwischen den beiden - ja, ich mag autosssh und geb ihm gern den Vorzug vor hackeligem #Portforwarding und #dyndns 🤷‍♂️ )

    Bin mal gespannt, ob das "schöner" arbeitet als #Passwords in der #Nextcloud. Das ist doch etwas umständlich für nicht so affine Familienmitglieder.