News for hackers. Stuff that matters.
Re:How To Safely Store A Password by Someone on Friday July 01, 2011 @09:11AM (#2718139)
If the client sends hash(password) to the server, hash(password), for all intents and purposes, _is_ the password.

After all, an attacker does not need to recover the password from the hash, all he has to do is capture the hash and replay it.

Re:How To Safely Store A Password by eneveu on Friday July 01, 2011 @09:44AM (#2718275)
Re:How To Safely Store A Password by shazow on Friday July 01, 2011 @11:22AM (#2718684)
On the upside, it is an improvement for the use-the-same-password-on-many-services users, assuming the hash is not trivial to reverse like md5.

At this point, I'm less worried about somebody getting access to some random startup I signed up for than I am about them using the leaked password to gain access to my other accounts.

(I've recently changed my password scheme to using a different one for every service, but this just puts me within a minority.)

Re:How To Safely Store A Password by zepolen on Friday July 01, 2011 @02:06PM (#2719437)
I'm no crypto expert but wouldn't using a nonce allow this approach to work?
Re:How To Safely Store A Password by pavpanchekha on Friday July 01, 2011 @10:39PM (#2720879)
How would you check the nonce? All your server gets is a black box hash.
Re:How To Safely Store A Password by IgorPartola on Saturday July 02, 2011 @10:23AM (#2721644)
Not a security expert here.

Doesn't http://en.wikipedia.org/wiki/Digest_access_authentication do this? Also the server could store the nonce in a session.