Re:Twitter Still Can't Keep Up with Its Flood of Junk Accoun...
by kgermino on Friday February 08, 2019 @10:41AM
(#19115187)
>For 10k passwords and 100ms per hash it is 90 hours of single threaded execution time.
That's 90 hours per account, multiply that by 326 million accounts and it's over a billion CPU days.
You can reduce it a lot (no need to spend time calculating the password for users who log in regularly, just wait for them to give it to you) but it's still a massive scale. Especially since the biggest risk comes from the millions of rarely used accounts.
Re:Twitter Still Can't Keep Up with Its Flood of Junk Accoun...
by llukas on Friday February 08, 2019 @11:37AM
(#19115896)
Correct. Forgot to multiply by 10^6
Re:Twitter Still Can't Keep Up with Its Flood of Junk Accoun...
by justsomedood on Friday February 08, 2019 @10:47AM
(#19115254)
I'm getting 90 million hours of single threaded execution time for 326 million users with 10k passwords each, and 100ms per hash.
Re:Twitter Still Can't Keep Up with Its Flood of Junk Accoun...
by giancarlostoro on Friday February 08, 2019 @10:35AM
(#19115130)
As somebody else commented, a quicker solution is to just force a password reset based on number of months since last login. If you havent logged in for over a year is a good rule of thumb.
There is no excuse not to do it, especially you need to do it only once per user (until password change).