I’m (probably) switching to Proton Pass from Bitwarden because its easier to create email aliases (all in one instead of making an alias with SimpleLogin, then copying that to Bitwarden and making a password there) but I’ve heard people saying not to use Proton Pass to not “put all your eggs in one basket”. Can someone explain what this means?

Thought if there is a way to generate those aliases within Bitwarden (using Proton’s alias not SimpleLogin’s as I’m going to be paying for Proton Unlimited anyways, I don’t wanna pay for SimpleLogin too) I’d appreciate it, as I prefer Bitwarden.

Thank you all :)

EDIT: I understand now. TL:DR: If one service dies you still have the other. Either way, turns out I can just grab my API Key from SimpleLogin and use it with Bitwarden, as thats what Proton uses anyways. Also the Proton Pass extension just shit itsself and I’m not a fan of Proton’s UI so I will be sticking with Bitwarden.

  • cosmic_cowboy@reddthat.com
    link
    fedilink
    English
    arrow-up
    5
    ·
    6 months ago

    It all depends on your risk tolerance and perceived threat model.

    I would recommend that if you do use Proton Pass in conjunction with your email, keep a backup KeePass file stored locally and in a few other places and update routinely.

    The Proton ecosystem definitely doesn’t fit everyone’s security model, but it is a massive leap compared to what Google and Apple offer.