2 ms·
Oh, sure. Storing the email address in a canonical column and using the provided address as a key helps. But I think the underlying bug is still there, because
by tptacek 3y ago
Oh, sure. Storing the email address in a canonical column and using the provided address as a key helps. But I think the underlying bug is still there, because the email code will still _accept_ the user input if you feed that to it.
- EGreg 3y agoPersonally, I like when people have usernames, and have to enter those, to receive a recovery message sent to the associated email. Or better yet, enter both username and email together. Because it's more likely the attacker won't know both. In any event, I have been recommending to everyone for years to use email aliases (that GMail and others support) as your login. Have a different one for each site, for example yourname+az@gmail.com for amazon. That way, you can avoid crap like this which is out of your control, since the attacker won't even be able to repeat your login email: https://www.wired.com/2012/08/apple-amazon-mat-honan-hacking/ https://www.wired.com/2012/08/apple-amazon-mat-honan-hacking...