03-26-2015, 08:40 AM
(03-26-2015, 08:29 AM)kartan Wrote: Atom is showing in his thread that you should expand your candidates with rules so your shaders get filled.
./hashcat-cliAVX2.bin rockyou1k.txt -r rules/best64.rule --stdout | ./oclHashcat64.bin -a 0 -m 2500 -d 2 -w 3 hashcat.hccap
That is different to your cat since your cat does not multiply the candidates by the best64.
But in the end your problem might not be fixed by that, 10k initial candidates is just not enough.
Looking at the post he has this:
Code:
./oclHashcat64.bin -a 0 -m 2500 -d 2 -w 3 hashcat.hccap rockyou1k.txt -r rules/best64.rule
vs
Code:
./hashcat-cliAVX2.bin rockyou1k.txt -r rules/best64.rule --stdout | ./oclHashcat64.bin -a 0 -m 2500 -d 2 -w 3 hashcat.hccap
Which both generate identical dictionaries unless I'm missing something, the only difference is that the second one gets the data via STDIN. They both use the same txt file and both use best64.rule to munge the wordlist.
So my impression is that he's saying if you just feed in the same dictionary via STDIN you'll get better parallelism.