News for hackers. Stuff that matters.
Re:Yahoo discloses hack of 1B accounts by jensvdh on Thursday December 15, 2016 @12:43AM (#13182716)
Never trust the client.
Re:Yahoo discloses hack of 1B accounts by XorNot on Thursday December 15, 2016 @01:40AM (#13182891)
This isn't about trusting the client: it's about your endpoint being able to only accept a SHA256 hash sum from the client (thus: length limited) while allowing the user to input arbitrarily long passwords.

They hash in the browser: the only way they can mess with it by producing silly outputs, but that only hurts them.

Re:Yahoo discloses hack of 1B accounts by libeclipse on Thursday December 15, 2016 @04:08AM (#13183376)
I can't think of any security implications of hashing on the client-side. What's your thinking?
Re:Yahoo discloses hack of 1B accounts by fnordsensei on Thursday December 15, 2016 @05:26AM (#13183625)
Does salting work if you hash in the browser?
Re:Yahoo discloses hack of 1B accounts by libeclipse on Thursday December 15, 2016 @05:36AM (#13183664)
Well in this case the hash would be passed to Bcrypt or Scrypt, which have built in salt support, so client side salting wouldn't matter.
Re:Yahoo discloses hack of 1B accounts by shawnz on Thursday December 15, 2016 @09:30AM (#13184729)
If the hashes are leaked, you could log in with them.
Re:Yahoo discloses hack of 1B accounts by XorNot on Thursday December 15, 2016 @07:43PM (#13190122)
Well serverside you store them as plaintext equivalents - i.e. salt+hash the hash. So a leak doesn't leak the user-side.