Re:Disqus Security Alert: User Info Breach
by akeck on Friday October 06, 2017 @07:44PM
(#15421296)
In the 2007-2012 era, SHA1 was common. Also, the salts will slow down cracking a little for passwords not already known.
[ Parent
| on HN ]
Re:Disqus Security Alert: User Info Breach
by wolf550e on Friday October 06, 2017 @10:07PM
(#15421858)
Nobody uses rainbow tables or cares to mitigate them. People care that GPU rigs get hundreds of billions of hashes-per-second[1] against a single-iteration salted hash. So all 8-char case-sensitive alphanumeric combinations can be checked in 18 minutes[2].
1 - https://gist.github.com/epixoip/a83d38f412b4737e99bbef804a27...
2 - (pow(26+26+10, 8) / 2*pow(10, 11)) / 60
Re:Disqus Security Alert: User Info Breach
by akvadrako on Saturday October 07, 2017 @04:20AM
(#15422881)
If you are attacking just one password, that makes sense. But if you want to check all the compromised accounts for easy to guess passwords, a salt will increase the cost.
Re:Disqus Security Alert: User Info Breach
by wolf550e on Saturday October 07, 2017 @11:20AM
(#15424088)
Salt won't save you. For checking most common passwords against stolen database, you try the top one million most common passwords against each hash, at a rate of 200,000 hashes per second.
A dictionary-based attack that tries variants and inserts digits and spends one second per hash will catch the less common passwords.