3 ms·
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 reco
by Someone 15y ago
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.
- eneveu 15y agoThis. Also, tptacek made a few interesting comments about client-side cryptography: http://news.ycombinator.com/item?id=1755713 http://news.ycombinator.com/item?id=1755713 http://news.ycombinator.com/item?id=1756394 http://news.ycombinator.com/item?id=1756394 http://news.ycombinator.com/item?id=1001007 http://news.ycombinator.com/item?id=1001007 http://news.ycombinator.com/item?id=1411621 http://news.ycombinator.com/item?id=1411621
- shazow 15y agoOn 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.)
- zepolen 15y agoI'm no crypto expert but wouldn't using a nonce allow this approach to work?
- pavpanchekha 15y agoHow would you check the nonce? All your server gets is a black box hash.
- IgorPartola 15y agoNot a security expert here. Doesn't http://en.wikipedia.org/wiki/Digest_access_authentication http://en.wikipedia.org/wiki/Digest_access_authentication do this? Also the server could store the nonce in a session.