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

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

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

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

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