bug in 0.40b4 - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html) +--- Forum: Old hashcat Support (https://hashcat.net/forum/forum-20.html) +--- Thread: bug in 0.40b4 (/thread-1176.html) |
bug in 0.40b4 - panda - 05-16-2012 A bug exists in hashcat 0.40b4 whereby all cracked hashes aren't removed from the target hashlist when using the "--remove" flag. This results in the perception that hashcat is not cracking all hashes on an initial run, as subsequent runs report new cracked hashes. eg. Code: $ sort -R /tmp/countries.dic | head -n 200 > /tmp/1.txt Output (1st run): Code: Added hashes from file /tmp/2.txt: 22200 (1 salts) Output (2nd run): Code: Added hashes from file /tmp/2.txt: 20191 (1 salts) NOTE: The hash is cracked in the initial run, but just not removed from the target hashlist. Code: $ tail -n 1 /tmp/3.txt RE: bug in 0.40b4 - M@LIK - 05-16-2012 Yup, I noticed something similar in v0.39. RE: bug in 0.40b4 - undeath - 05-16-2012 did you uniq the hash file before? RE: bug in 0.40b4 - panda - 05-16-2012 Yes. I dont show it in the test example above, but in "production" the hashes are uniq and the problem persists. |