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.
If a service is ever compromised, you would have chosen to consolidate information that would lead you to be more greatly vulnerable than if you had spread over multiple services.
The idea is quite simple. If you put all your eggs into one basket, if that basket breaks, you’re screwed.
If we put this into context, this would mean that you would, for example, use all of Proton’s services and when Proton does something bad, now your entire suite of services is fucked.
A (small) part of not putting all your eggs in one basket is also avoiding vender lock-in. Having your personal email with proton, and your password manager with them makes it very difficult to switch in the future if you need to.
On a side note, I use anonaddy (now Addy.io). It allows you to create email aliases on the fly. So when I sign up for a new account somewhere, I generally make up some email like “[email protected]” for the email and save that right to bitwarden.
Looks like simplelogin supports the same thing https://simplelogin.io/blog/subdomains/
PS. Using your own domain name is a great way to avoid vender lock-in =)
