161
What types of services are you not willing to self-host? (lemmy.world)
submitted 3 years ago by to c/selfhosted@lemmy.world
125 comments fedilink hide all child comments
 

For example, something that is too complex for your comfort level, a security concern, or maybe your hardware can’t keep up with the service’s needs?

you are viewing a single comment's thread
view the rest of the comments
[–] 82 points 3 years ago (4 children)

Password manager like Bitwarden. I'd rather they take care of it for me. The consequences would be too great if I messed it up.

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 17 points 3 years ago (2 children)

    Smart move, unless you really know what you're doing and have redundancy. When I first made the switch from Lastpass to Bitwarden I had tried to host the vault myself instead of using the cloud version, which worked fine right up until the moment I had a server outage and lost access to all my passwords.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [+] 20 points 3 years ago* (last edited 2 years ago) (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 3 years ago (1 child)

    I think that's what's kept me at KeePass rather than moving to something like Bitwarden. Since it's file-level encryption, anything that can serve files can also serve my KeePass database. When I upgrade servers or change to different services, restoring my database is as simple as throwing the file into that new service and going on with my life.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 13 points 3 years ago (1 child)

    Eh, the clients all cache your vault. It shouldn't be a huge issue for it to be down even for a few days.

    But I do upload encrypted backups of the server every 6 hours to cloud storage

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 3 years ago (2 children)

    Oh man, that's actually really good advice! I recently switched to Vaultwarden, but you're right: If my server goes down, I can't even restart it, because the password for my account is in there! Damn! Close call!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 17 points 3 years ago

    Well with bitwarden/vaultwarden you can have a copy of your entire vault on your phone or computer or both... so even if your server was totally dead, you'd have access to your passwords. Solid backups is a must, I follow the 3-2-1 rule on super critical systems (like vaultwarden) and test that you can actually recover. Something as simple as spinning up a VPS, testing a restore, testing access, see if that could work in a pinch until you get your server back online, then tear it down. Linode is very cheap for this kind of testing, it'd only cost you a few pennies to run a "dr" test of your critical systems. Of course you still want to secure it, I'd recommend wireguard or tailscale instead of opening access to your DR node to the internet, but as a temporary test it's probably fine if your running patched up to date versions of docker, vaultwarden, and I'd always recommend putting a reverse proxy in front like nginx.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 3 years ago* (last edited 3 years ago)

    I still don't get why people want to have cloud-based password managers. Keepass works in all major platforms, it's just one file, which it is super easy to sync and/or merge. It can integrate with your browser/Os if you want, but otherwise the surface attack is basically zero.

  • permalink
  • fedilink
  • source
  • parent