5 ms·
Sounds alarming, but not true. If you don’t know the salt, you are not cracking an MD5 password on basic hardware. You are probably not cracking the password in
by xwdv 7y ago
Sounds alarming, but not true. If you don’t know the salt, you are not cracking an MD5 password on basic hardware. You are probably not cracking the password in any reasonable time, period.
And when you have a unique salt per user, that’s basically game over.
- cm2187 7y agoUsually the salt is stored along the login and password.
- xwdv 7y agoThat’s not on the list of things stolen, so the passwords are safe. The salts were kept elsewhere, as they should be.
- txcwpalpha 7y agoDo you have some insider information, or where are you getting this? If the hackers were able to steal all of the other login information, the salts were almost certainly stolen along with the hashes.
- cm2187 7y agoThe article doesn't mention customer id and account creation date, though these records were almost certainly along the login and passwords also. It's general news article.
- Thorrez 7y agoWhy should salts be stored elsewhere? If you have some high-security other storage, why don't you store the password hashes there?
- txcwpalpha 7y agoLook up benchmarks for cracking MD5 hashes. You can crack an MD5 hash of an average length password (and StockX only requires an 8 character password), even with a salt, within seconds with a single consumer grade GPU. A hacker group with any serious setup for hash cracking has almost certainly already cracked most, if not all, of these hashes.
- ryanlol 7y agoUnless you presume that you know the salt your comment is utter nonsense. The fact that the article says “believed to be” strongly suggests that things are not as simple as they’re “believed to be”, because if the passwords were easy to crack that’d be trivial to prove.
- thenewnewguy 7y agoIf the hash has been leaked then why is there reason to believe the salt _hasn't_ been leaked?
- deleted 7y ago[deleted]
- eterm 7y agoIf the passwords have leaked it's safe to assume the salts have, typically they're stored side by side.
- alasdair_ 7y ago>Unless you presume that you know the salt your comment is utter nonsense. Usually the attacker will also know the salts in a breach of this type, unless the company did something clever with the salts (doubtful since they used MD5).
- ryanlol 7y agoThe fact that the article says “believed to be” strongly suggests that things are not as simple as they’re “believed to be”, because if the passwords were easy to crack that’d be trivial to prove. We don’t know how the passwords are hashed. All we have is a journo guessing.
- deleted 7y ago[deleted]
- xwdv 7y ago
- viraptor 7y agoIn 2012: https://www.zdnet.com/article/25-gpus-devour-password-hashes-at-up-to-348-billion-per-second/ https://www.zdnet.com/article/25-gpus-devour-password-hashes... That's 7.2 billion hashes per second per single Radeon GPU for md5. For 8 character password with numbers and letters that's 8.5 hours max and 4.25h on average.. The numbers only got better since then, I expect it's at least halved for this year's hardware. (edit: 1080ti does 32GHps, so yeah... make that 1h on average https://www.servethehome.com/password-cracking-with-8x-nvidia-gtx-1080-ti-gpus/ https://www.servethehome.com/password-cracking-with-8x-nvidi... ) Assumptions, not specified in the article: - The salt is stored with the hash (this is a standard approach) - It's only a trivial implementation with a single round of MD5. If they used multiple rounds or PBKDF1, then the hash choice doesn't matter as much.
- txcwpalpha 7y agoThose time periods also assume that you're just blindly cracking every possible 8-character combination, but you don't have to do that. Running your cracker against a password list like rockyou will probably get you 90%+ of passwords cracked in less than one second per hash with that same hardware.
- SkyPuncher 7y agoYou need to update yourself on the vulnerability of MD5. 5 years ago, a run of the mill gaming PC could crack an MD5 hash in a reasonable amount of time. Worst case, you'd have to let it run overnight. One of the big issues is collisions. You might not find the original key, but you'd find something that hashed to the equivalent output.
- FDSGSG 7y ago> Worst case, you'd have to let it run overnight. AFAIK the best current preimage attack against MD5 gives you a complexity of 2^123.4. Even if you had every computer in the world working on this you'd never succeed. >One of the big issues is collisions. You might not find the original key, but you'd find something that hashed to the equivalent output. This is false. There does not exist a feasible preimage attack against MD5.