I’m using Vaultgarden. Things are okay after losing my SSD yesterday morning. My strategy worked… HDD for data, SSD for the OS. I promptly found an available drive, installed Linux mint and recovered.

But that was scary. I keep a backup on another computer. The only way to actually run it and see the passwords needed to do anything was thru my phone. I was lucky that somehow the database was available offline. But if I had run out of battery I would be extremely screwed.

So I’ve decided the Vaultgarden is encumbered by not really having a local reliable copy. Maybe I’m wrong, but as I understand, if your server goes down and you log out, you’re screwed… No more passwords until your server is up again. I find that to be extremely stupid unless I was protecting my severed testicles… No wait, that would be way worse.

So I’d there a server + local system? Like Joplin… You can write notes all day with no server at all. The server just Synchronizes it all. In the past I used syncthing and I will continue using it. One thought was to have an automated backup from Vaultgarden that was automatically synced to my various devices as a Keypass database.

  • zikzak025@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    1 day ago

    Just don’t count on the current Bitwarden client being compatible with Vaultwarden forever. Bitwarden’s new CEO is pushing to make more profit wherever possible, and recently rescinded the statement from the company’s website that the client would be free forever.

    They’ll never be able to walk back the open source nature of the product, but they can choose to make their client incompatible with Vaultwarden and push for the centrally hosted option as the only option.

    Not sure if anyone’s forked the Bitwarden client yet, but that’s how I’d start using Vaultwarden if the option exists.

    Or, you know, skip the headache and just start using Keepass.