News for hackers. Stuff that matters.
Re:Authentication Cheat Sheet by mjevans on Tuesday February 03, 2015 @04:01AM (#8989451)
Think about what you've just said. How insecure is sending the password (hopefully over an HTTPS connection!) to a remote server?
Re:Authentication Cheat Sheet by lstamour on Tuesday February 03, 2015 @09:36AM (#8990476)
How else do you allow someone to use a password to login? I suppose you could run the hash locally if they have JavaScript-- but if they don't, then what? (Edit: Good point, all the hash achieves is that the user's entry isn't sent in clear text -- of course, the hash itself then becomes the password for the purposes of authorization.)
Re:Authentication Cheat Sheet by slavak on Tuesday February 03, 2015 @09:59AM (#8990625)
Running a hash locally is equally useless. You've effectively turned the hashed value into the password itself, achieving nothing.

There are secure key-exchange schemes that don't require sending over the raw password, but this isn't an example of one.

Re:Authentication Cheat Sheet by nacs on Tuesday February 03, 2015 @06:24PM (#8994273)
Just about every signup and login form does this (and yes preferably over TLS only). What is the problem with it?

The alternative is browser-side encryption of the password before sending but that will get @tptacek rightfully punching you in the face for even mentioning it.