Posts: 55
Threads: 17
Joined: Jun 2014
In your opinion, what's the best way to tackle bcrypt with a cost of 12 (ie $2a$12$...)?
While I think using the GPU would the best choice when we deal with dictionary + rules attacks, what about when you try something easier?
For example bruteforce for digits only passwords or very short ones?
Is the GPU still the best tool or in such cases we should fallback on CPU?
Any thoughts on that?
Posts: 30
Threads: 1
Joined: May 2015
Any coincidence that the AM leak uses bycrypt?
All those lovely passwords would be great in a dictionary, but I doubt many will be obtainable.
Try using a really really short dictionary, maybe the top few hundred passwords, no more. A quick benchmark gives me about 400 H/s on GPU (teeny little laptop AMD one) and 1.8k H/s on CPU, so best off using CPU I think.
Posts: 5
Threads: 0
Joined: Jul 2015
My system can do 28k h/s for bcrypt, so not impossible, just slow enough to be annoying. Try using a custom word list that is tailored to the dump. Considering what you are probably trying to crack then think about words that they would use.
Posts: 5,185
Threads: 230
Joined: Apr 2010
The major problem with the AM dump is not the it is bcrypt (well it's slower than MD5, yes) but the huge number of unique salts. If you target one specific hash it's still possible to process a normal wordlist in a normal time window.
Posts: 14
Threads: 6
Joined: Apr 2015
I think the official best way to tackle it would be to combine forces using distributed hash cracking.
I can set it all up, but the question is, who would be interested in running hashtopus every day to take down that algorithm?
Posts: 2,936
Threads: 12
Joined: May 2012
I'm not sure you can math.
