News for hackers. Stuff that matters.
Re:Yahoo discloses hack of 1B accounts by cookiecaper on Wednesday December 14, 2016 @08:57PM (#13181703)
Yep, people who've run marginally popular sites have dealt with this before. Give someone a text box and watch them try to stuff 4GB of content in it. There has to be a cutoff somewhere, but as you note, it should be well outside of the realm of reasonable password lengths (hundreds of characters).
Re:Yahoo discloses hack of 1B accounts by jsjohnst on Wednesday December 14, 2016 @09:11PM (#13181761)
GitHub is the only website I can think of off the top of my head that doesn't limit to an arbitrarily small number (aka <100). Do you name any other "major" websites that allow 100 character passwords?
Re:Yahoo discloses hack of 1B accounts by snowpanda on Thursday December 15, 2016 @01:45AM (#13182914)
Re:Yahoo discloses hack of 1B accounts by amichal on Thursday December 15, 2016 @12:21PM (#13186248)
Anything built with the popular rails gem devise allows 128 by default [1]

https://github.com/plataformatec/devise/blob/88724e10adaf9ff...

Re:Yahoo discloses hack of 1B accounts by XorNot on Wednesday December 14, 2016 @11:09PM (#13182325)
Hash the password locally (you are serving JavaScript over SSL right?) and only send the SHA256.
Re:Yahoo discloses hack of 1B accounts by zeveb on Thursday December 15, 2016 @04:34AM (#13183454)
That would lock out anyone who chooses not to execute your JavaScript.

Requiring me to trust your code in order for you to decide whether or not to trust me is asking too much.

Re:Yahoo discloses hack of 1B accounts by 0xfeba on Thursday December 15, 2016 @09:10AM (#13184621)
How would you know that the hash is of a password of sufficient entropy?
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.