I use an algorithm. In short: 1. Memorize some base password 2. Memorize a way in which you mutate that password based on the name/type/other of the service logging in to. Eg. Hunter2 becomes eHunterG8 Because my example algorithm cares about Google's first letter, length, and service type: email. It allows every password to be different but you only memorize two things. It is meant to be a "good enough" solution tha…
Doesn't this compromise all of your passwords if one of your passwords is discovered? Sure, it would take a bit of thinking to realize what each part refers to and even realize that your password has some sort of generation algorithm, but it would be a bit more secure to hash that password in some way. That's why I like using LessPass (even though people talk a bit of shit about it whenever it's mentioned on HackerNe…
I've been trying to understand password managers for a while. My workplace forces us to use one.
But what you've said doesn't make sense. If your "master password" used in the password manager is discovered, then all your passwords are compromised.
If my laptop or phone gets stolen and someone knows the password from my password manager, then I'm done for.
I choose to follow the algorithm approach too. Even though it's BS.