10-22-2012, 04:03 AM
(This post was last modified: 10-22-2012, 04:36 AM by Kgx Pnqvhm.)
A quick speed comparison using the word list from Cain against a group of 60 hashes, with no rules, showed that CPU hashcat would take 2 days, whlie the GPU hashcat-plus would take 26 days (for the -a 1 attacks).
If this is really the expected speed difference, one should do simple no-rule attacks in regular hashcats. Combining two dictionaries can be done by just merging them together.
Very simple rules like "u" or "c" could be done on a word list before being fed back into regular hashcat, and still be faster than GPU hashcat. (Along with the advantage of getting over 15 characters.) (So maybe that T0 T3 on the combined candidate would be faster than -j u on a left side in GPU 'plus?)
So one would use GPU hashcat for combinator attacks only if complicated rules were involved that would be impractical to do beforehand on word lists for regular hashcat?
As another comparison, I ran CPU hashcat with a rule file with just ":" to set up the script to use, but running it for a while never gave me an estimate of how long it would take. This must be some sort of bug?
If this is really the expected speed difference, one should do simple no-rule attacks in regular hashcats. Combining two dictionaries can be done by just merging them together.
Very simple rules like "u" or "c" could be done on a word list before being fed back into regular hashcat, and still be faster than GPU hashcat. (Along with the advantage of getting over 15 characters.) (So maybe that T0 T3 on the combined candidate would be faster than -j u on a left side in GPU 'plus?)
So one would use GPU hashcat for combinator attacks only if complicated rules were involved that would be impractical to do beforehand on word lists for regular hashcat?
As another comparison, I ran CPU hashcat with a rule file with just ":" to set up the script to use, but running it for a while never gave me an estimate of how long it would take. This must be some sort of bug?