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: the quantity of rules in the rule based attack
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
hello everyone.

I'm new to hashcat and I have a question about the rule based attack. My command is as below:

~/hashcat/hashcat/hashcat -a 0 -m 0 ../hashs/md5.hash -r ./rules/tempRule_1 --debug-mode=4 --debug-file=./temp_debug_rule ./dicInLengthOrder --remove -o ./results/result_1

there are 49 rules in my rule file "tempRule_1", but in the stdout infomation, there are 2401 rules in total. The output infomation is as below

hashcat (v3.10-184-g458d6b3) starting...

OpenCL Platform #1: NVIDIA Corporation          
======================================
- Device #1: GeForce GTX 970, 1009/4036 MB allocatable, 13MCU

Hashes: 25417 digests; 25417 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 2401
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Salt
* Raw-Hash
........
........
Rules.Type.....: File (./rules/tempRule_1), File (./rules/tempRule_1)
Input.Mode.....: File (./dicInLengthOrder)
Hash.Target....: File (../hashs/md5.hash)
Hash.Type......: MD5
Time.Started...: Thu Apr 27 15:28:47 2017 (2 secs)
Time.Estimated.: Thu Apr 27 15:29:50 2017 (59 secs)
Speed.Dev.#1...:  1262.1 MH/s (10.08ms)
Recovered......: 0/25417 (0.00%) Digests, 0/1 (0.00%) Salts
Recovered/Time.: CUR:N/A,N/A,N/A AVG:0.00,0.00,0.00 (Min,Hour,Day)
Progress.......: 2648369152/77992057556 (3.40%)
Rejected.......: 0/2648369152 (0.00%)
Restore.Point..: 878592/32483156 (2.70%)

as 2401 = 49 * 49, it seems that hashcat combines the rules in my rule file. How can I just use the rules in my rule file and not combine them?

thanks.
This would usually happen when you specify -r multiple times in the comand line, but you don't seem to be doing that.

Please try with the latest version. It might be a bug.
(04-27-2017, 11:40 AM)undeath Wrote: [ -> ]This would usually happen when you specify -r multiple times in the comand line, but you don't seem to be doing that.

Please try with the latest version. It might be a bug.

It really works. Thanks a lot.