3 ms·
Assuming that you run your own login service like Facebook does, you always have access to your user's passwords at least once because at some point you have to
by kibwen 12y ago
Assuming that you run your own login service like Facebook does, you always have access to your user's passwords at least once because at some point you have to take the raw password and hash it. Facebook just creates two variations of the user's password and stores the hashes for all three of them.
- ssmoot 12y agoAll three of them? The Hash for the password as-typed, another for as-typed.invert(). What's the third? I feel like I'm missing something obvious. :-/
- andrewaylett 12y agoMac-style caps-lock, which doesn't invert again with shift, and PC-style, which does.
- plorkyeran 12y agoFirst letter uppercase, for mobile devices that default to shift being on for just the first letter.
- TheCoelacanth 12y agoPossibly for the two different types of caps lock. The kind that inverts the case of everything and the kind that makes everything uppercase.
- ssmoot 12y agoI never noticed that. (I switched to Macs around 8 years ago.) Huh. In that case I guess I have to wonder what the point is? Why store three hashes as opposed to just upper-casing the plain-text before hashing? You end up storing fewer variations, and it makes no functional security difference to the front-end (since any attacker would just .toUpperCase() their inputs anyways)? At least best I can reason.