News for hackers. Stuff that matters.
Re:Yahoo discloses hack of 1B accounts by bschwindHN on Thursday December 15, 2016 @02:15AM (#13183014)
Is "just use scrypt" an acceptable answer then? I'm not a security expert and I don't know the advantages of one over the other.
Re:Yahoo discloses hack of 1B accounts by amenghra on Thursday December 15, 2016 @04:08AM (#13183375)
Yes, scrypt is a perfectly fine password hash.

If you are currently using something else (say salted md5 or even just plain md5), you can migrate your passwords to scrpyt(current_hash()) without having to change everyone's password and/or wait for everyone to log in.

See also this comment thread: https://news.ycombinator.com/item?id=12549110

Re:Yahoo discloses hack of 1B accounts by aaronbasssett on Thursday December 15, 2016 @05:16AM (#13183594)
Don't do that. You've essentially just turned the old hashes into plain-text passwords, and how sure are you that those hashes don't exist in backups anywhere?
Re:Yahoo discloses hack of 1B accounts by rietta on Thursday December 15, 2016 @08:34AM (#13184437)
No, not exactly. An adversary who has the old hash, but not the plaintext that it represents cannot login because scrypt(H(H(value))) != scrypt(H(value)). This is not considering the offline crackability of a compromised hash. But there are legitimate situations where upgrading the password backing to a modern slow hash is preferable to continuing to use the old hash or worse storing the old hash as a field for a long time so that when a breach happens both the new and old hashes are available.

There are user experience battles when talking about forcing a million users to change their passwords in a real system. Hashing the hash may be vastly preferable to management nixing the security upgrade. A password updating schema that changes the hash as users login and eventually locking the accounts of users who have not logged in for an extended period of time can accomplish rolling the hashes without having to tell users to change their passwords.

Re:Yahoo discloses hack of 1B accounts by StavrosK on Thursday December 15, 2016 @06:34AM (#13183885)
Not if you mark the converted versions and try scrypt(oldhash()) on users authenticating with them.
Re:Yahoo discloses hack of 1B accounts by fractal618 on Thursday December 15, 2016 @06:37AM (#13183892)
Woah! Very good point!
Re:Yahoo discloses hack of 1B accounts by kijin on Thursday December 15, 2016 @05:33AM (#13183649)
scrypt is okay if you use it correctly. It's too easy to use it incorrectly, though, because scrypt is a low-level algorithm that wasn't specifically designed for password storage. [1]

http://blog.ircmaxell.com/2014/03/why-i-dont-recommend-scryp...

In order to be able to tell people to "just use scrypt", we would need to have a sort of standard wrapper that uses the correct parameters by default and produces identical results in every common programming language.