Please note, this is a STATIC archive of website hashcat.net from October 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: stdout speed between hashcat-cli64.exe V2.0 and hashcat64 v5.1.0
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have been learning how rules modify password candidates in hashcat and have found using --stdout to a text file very useful.

I have noticed a significant difference in speed between hashcat-cli64.exe V2.0 and hashcat64 v5.1.0. but not in the way I expected.

For speed testing purposes I used a 118MB rule file and a single password candidate to modify.

A sample (not all) of the batch commands I used.

hashcat-cli64.exe V2.0
hashcat-cli64.exe -r TestRules.rule TestPass.txt --stdout >> TestOutput.txt
hashcat-cli64.exe -n 64 -r TestRules.rule TestPass.txt --stdout >> TestOutput.txt

hashcat64 v5.1.0
hashcat64 -r TestRules.rule TestPass.txt --stdout >> TestOutput.txt
hashcat64 -D 1 -r TestRules.rule TestPass.txt --stdout >> TestOutput.txt
hashcat64 -w 3 -r TestRules.rule TestPass.txt --stdout >> TestOutput.txt

I tried combinations of -w (hashcat64 v5.1.0.) and -n (hashcat-cli64.exe V2.0), or none at all, in my batch scripts with little to no effect.

Every time both output files were almost identical except for 10 - 20 lines out of approx 18921740 lines so the output is not significantly different which would have otherwise explained it.

The speed difference is huge:

hashcat-cli64.exe V2.0 - generally takes approx 70 seconds

hashcat64 v5.1.0 - generally takes approx 420 seconds


My system:

No GPU hashcat would be interested in so I use CPU option.
Win7 64bit Sp1 and all updates.

Could someone please let me know if I am using the wrong commands or if hashcat64 v5.1.0 is supposed to take longer for some technical reason, perhaps better validity checking etc?

Thank you