|
bug in 0.40b4
|
|
05-16-2012, 11:57 AM
Post: #1
|
|||
|
|||
|
bug in 0.40b4
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.txtOutput (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 |
|||
|
05-16-2012, 12:08 PM
Post: #2
|
|||
|
|||
|
RE: bug in 0.40b4
Yup, I noticed something similar in v0.39.
|
|||
|
05-16-2012, 05:43 PM
Post: #3
|
|||
|
|||
|
RE: bug in 0.40b4
did you uniq the hash file before?
|
|||
|
05-16-2012, 05:51 PM
Post: #4
|
|||
|
|||
|
RE: bug in 0.40b4
Yes. I dont show it in the test example above, but in "production" the hashes are uniq and the problem persists.
|
|||
|
« Next Oldest | Next Newest »
|
Search
Member List
Calendar
Help



