11-27-2017, 11:54 AM
Thanks for the references and explanation! I'm still interested to find out how this works exactly.
Related to my first question on base:mod of the --help output:
"[Amplifying is accomplished] by splitting attacks up into two loops: a base loop, and a modifier loop. The base loop is executed on the host and contains the initial password candidates. The modifier loop is executed on the compute device, and generates the rest of the candidates from the initial candidates on the device directly. The modifier loop is our amplifier, that's where our acceleration comes from." https://hashcat.net/forum/thread-5287-po...l#pid28724
A minimum working example:
According to the FAQ 129988 is correct as the rules are never taken into account for -a 0, which seems strange.
The calculation of 'hashcat legacy' seems to make more sense for -a 0 as the "number of words in wordlist multiplied by number of rules in rule file"
Maybe atom could clarify why this changed?
Related to my first question on base:mod of the --help output:
"[Amplifying is accomplished] by splitting attacks up into two loops: a base loop, and a modifier loop. The base loop is executed on the host and contains the initial password candidates. The modifier loop is executed on the compute device, and generates the rest of the candidates from the initial candidates on the device directly. The modifier loop is our amplifier, that's where our acceleration comes from." https://hashcat.net/forum/thread-5287-po...l#pid28724
A minimum working example:
Code:
$ ./hashcat -m 0 -a 0 example.dict -r rules/best64.rule --keyspace
129988
$ ./hashcat -m 0 -a 0 example.dict --keyspace
129988According to the FAQ 129988 is correct as the rules are never taken into account for -a 0, which seems strange.
The calculation of 'hashcat legacy' seems to make more sense for -a 0 as the "number of words in wordlist multiplied by number of rules in rule file"
Maybe atom could clarify why this changed?