5 ms·
During the Defcon password cracking contest this year, there were 5,150 bcrypt hashes. In 48 hours, only 76 of them were cracked. In contrast, there were 8,544
by 16s 14y ago
During the Defcon password cracking contest this year, there were 5,150 bcrypt hashes. In 48 hours, only 76 of them were cracked. In contrast, there were 8,544 plain sha1 hashes, 4,111 of those were cracked. You can see the full list of hash types and how many were cracked here:
http://contest-2012.korelogic.com/stats.html http://contest-2012.korelogic.com/stats.html
This is probably the premier password cracking contest in the world. I placed 7th overall and was first to crack most of the TrueCrypt volumes and I despise attempting to crack bcrypt hashes (most sane people do). You really have to try and crack them for yourself to fully appreciate how difficult and slow they are to attack.
- JakeSc 14y agoWere most people using rainbow tables or brute forcing do crack the hashes?
- baudehlo 14y agoThe point of bcrypt is you can't use a rainbow table.
- tptacek 14y agoNo modern hash function, including "salted SHA" and Unix crypt() is vulnerable to "rainbow tables". Rainbow tables work exclusively against the dumbest possible hashing schemes. Bcrypt isn't a defense against "rainbow tables"; the hash function bcrypt supplanted (PHK's MD5 crypt) was also not "rainbow-table-able".
- ZoFreX 14y agoCorrect me if I'm wrong but couldn't you construct rainbow tables for any hash function which takes a single input (including salted SHA, if the salt is the same for all passwords)? Of course, you'd need a seriously large set of passwords on your hands for it to be worth the effort, but it could be done right? (Possibly worth mentioning, possibly not, that if your salts are extremely weak then the combined hash might show up in regular rainbow tables, whether your salts are unique or not - it seems unlikely this would ever happen in practice though)
- danielweber 14y agoThe point of rainbow tables is that you can pre-calculate them. I wrote some myself for fun, and it does take a while to build stuff up. Even if someone was dumb enough to use the same salt everywhere, once you know that you would just start brute-forcing, not building a rainbow table for the joy of searching it. (Unless you are into that like me.)
- drivebyacct2 14y agoIf you're using the same salt for everything, you've very nearly defeated the purpose of using a salt. No salt means that a password hashes to the same thing, everywhere. A site specific salt means that someone can generate rainbow table to efficiently attack all accounts. A user specific salt means that generating rainbow tables is effectively the same (complexity) as brute-forcing.
- ZoFreX 14y ago> If you're using the same salt for everything, you've very nearly defeated the purpose of using a salt. I'm aware - it's hardly a rare use-case though (sadly).