News for hackers. Stuff that matters.
Re:Dropbox: Security update & new features by mnutt on Tuesday July 31, 2012 @08:54PM (#4320551)
They wouldn't have to store your password in plaintext to determine that. They could just hash commonly used passwords and compare the hashes to yours.
Re:Dropbox: Security update & new features by wizardishungry on Tuesday July 31, 2012 @08:56PM (#4320554)
If the number of salts used in the system is equal to the number of users, this could be expensive.
Re:Dropbox: Security update & new features by jarito on Tuesday July 31, 2012 @08:58PM (#4320562)
They will just check your password against a list of 'bad' passwords when you log in. No need to brute force the stored hash.
Re:Dropbox: Security update & new features by wizardishungry on Tuesday July 31, 2012 @09:12PM (#4320613)
A little bit of googling makes it seem like auth tokens are not sent it plaintext over HTTPS but are authenticated using challenge response – http://forums.dropbox.com/topic.php?id=47952 The WWW site may differ.
Re:Dropbox: Security update & new features by wizardishungry on Tuesday July 31, 2012 @09:04PM (#4320587)
Obviously that would work, but not if you're using Challenge-response authentication. In general, I don't think people bother with now that when using https.
Re:Dropbox: Security update & new features by tedunangst on Tuesday July 31, 2012 @10:35PM (#4320913)
Assuming they use straight up salted sha256, my five year old core2 laptop does at least 10,000 per second, per core. They could check every user for the top 10k passwords for a few hundred bucks of EC2 time.
Re:Dropbox: Security update & new features by xentronium on Wednesday August 01, 2012 @06:45AM (#4322137)
Why do you assume that?