Unexpected output when using rules to stdout
#5
(02-08-2023, 12:55 AM)WPA_Catcher Wrote: Hmm...

Using the latest beta

There still seems to be something strange about hashcat outputting plain passwords, through rules, to a text file.

I ran a single (solitary) password through a rule file and saved the output to "new_passwords.txt"

I hashed all the new words in "new_passwords.txt".

I then used the same plain text password and ran it through the same rule file to crack all the hashes I had just created.

What I do not understand is that on some occasions I am cracking less than 20%

Why am I not cracking 100% of the passwords created with the very same password and rule file I used to make the hashes?

because --stdout seems to be still broken

your "new_passwords.txt" contains passwords which are not really generated by your ruleset, but outputted to file because of broken --stdout, then you hashed these "right and wrong candidates", but when attacking these hashes with your single password + ruleset, the gerated passwordcandidates  are "right" so the wrong candidates are missing, as result, you dont crack 100% but only the "correct" generated passes
Reply


Messages In This Thread
RE: Unexpected output when using rules to stdout - by Snoopy - 02-08-2023, 03:10 PM