3 ms·
The attacker does, of course, have the salts as well, since they're part of the hash. I don't see how they can try hundreds of billions of password combinations
by StavrosK 14y ago
The attacker does, of course, have the salts as well, since they're part of the hash. I don't see how they can try hundreds of billions of password combinations per second, though.
- bcoates 14y agohttp://securityledger.com/new-25-gpu-monster-devours-passwords-in-seconds/ http://securityledger.com/new-25-gpu-monster-devours-passwor... 25 late 2012 vintage GPUs gets you 180 billion MD5 tries per second. With a fairly modest budget you can rent a whole lot more GPU power than that. A little Googling gets me several companies offering password hash cracking as a service.
- elithrar 14y ago> 25 late 2012 vintage GPUs gets you 180 billion MD5 tries per second. With a fairly modest budget you can rent a whole lot more GPU power than that. A little Googling gets me several companies offering password hash cracking as a service. But we're assuming, at the very least, that they're not using MD5 and are instead using SHA-2/SHA-256 or (s|b)crypt. There's an order of magnitude difference between brute forcing MD5 and brute forcing something better.
- floody-berry 14y agohttp://hashcat.net/oclhashcat-plus/ http://hashcat.net/oclhashcat-plus/ MD5 is 2-3x as fast as SHA-1 MD5 is 5-7x as fast as SHA-256 I don't know why anyone would assume they are using anything better than MD5/SHA-1 considering the history of incidents like this.
- floody-berry 14y agohttps://www.livingsocial.com/createpassword https://www.livingsocial.com/createpassword: "LivingSocial passwords were hashed with SHA1 using a random 40 byte salt." Shocker!