03-14-2011, 10:49 AM
awesome! nice catch again, tommie_c! it is a bug in the RULE_OP_REJECT_CONTAINS '%' rule.
the bug was the following:
it should do: reject the word unless it contains at least N instances of X
but it actually did: reject the word unless it contains exactly N instances of X
fixlog:
the bug was the following:
it should do: reject the word unless it contains at least N instances of X
but it actually did: reject the word unless it contains exactly N instances of X
fixlog:
Code:
root@thumbstone:~/dev/projects/hashcat/hashcat-0.37# echo -n blTckhTt1 | md5sum
0fd34e9f1684b1bf309aee37acb72ded -
root@thumbstone:~/dev/projects/hashcat/hashcat-0.37# echo 0fd34e9f1684b1bf309aee37acb72ded > hash
root@thumbstone:~/dev/projects/hashcat/hashcat-0.37# echo blackhat1 > word
root@thumbstone:~/dev/projects/hashcat/hashcat-0.37# cat > rule
%1asaT
root@thumbstone:~/dev/projects/hashcat/hashcat-0.37# ./hashcat-cli64.bin hash word -r rule
Initializing with 8 threads and 32mb segment-size...
NOTE: press enter for status-screen
Added hashes from file hash: 1 (1 salts)
Activating quick-digest mode for single-hash
Added rules from file rule: 1
0fd34e9f1684b1bf309aee37acb72ded:blTckhTt1
All hashes have been recovered
root@thumbstone:~/dev/projects/hashcat/hashcat-0.37#