News for hackers. Stuff that matters.
Re:Password Hijacking Security Incident and Response by tptacek on Wednesday January 09, 2013 @04:59PM (#5033819)
The only way this fiddly scheme could be secure is if the randomizing information (that prevents an attacker from brute forcing the hash against all possible email addresses) is different for every token and thus stored somewhere serverside. It is no more secure than simply sending the user a random token, but has all the logistical challenges of storing a token.

So just use the token.

Re:Password Hijacking Security Incident and Response by codegeek on Wednesday January 09, 2013 @05:01PM (#5033828)
"stored somewhere serverside"

So you are a strong advocate of generating the token and storing it in the db.

Re:Password Hijacking Security Incident and Response by tptacek on Wednesday January 09, 2013 @05:04PM (#5033847)
That is the simplest possible answer and so it's the one you should use.