4 ms·
One suitable option is to memorize an algorithm as a password: Say, given a site, create a password as: HardcodedChars+siteName+len(siteName)+symbolInKeyboard
by xtracto 5y ago
One suitable option is to memorize an algorithm as a password:
Say, given a site, create a password as:
HardcodedChars+siteName+len(siteName)+symbolInKeyboardOf(lenSiteName)+len(TLD)*N+hardcodedChars
So gmail.com would be something like
Chad1Gmail5%9Foo@
And then use that algorithm for generating all passwords.
- udia 5y agoThis was my strategy for some time, but I switched to using a proper password manager (Bitwarden). If your algorithm is discovered you're in as much trouble as if you used the same password across multiple sites.
- sumedh 5y ago> One suitable option is to memorize an algorithm as a password: You lost 99% of people here.
- dubcanada 5y agoWhat happens if siteName changes? What happens if you lose your memory? Wait was it "TransferWise" or "Transferwise" or "Wise" or "wise" or "transferwise"? I don't hate the idea, but what happens when you stumble upon a website that does not accept % in passwords, or needs less then 8 characters or one of the other random things that do exist? Then you have an algo for this, and a algo for that, you end up back at the same place.
- panda-giddiness 5y agoMoreover, how does an algorithm handle password resets?
- xtracto 5y agoWhat happens if you lose the PostIT where you had your password? What happens if you lose your KeePass file? What happens if your password manager service goes out surprisingly, or gets hacked and someone deletes their DB? What if, what if...!