atom: ahhh. I think I know what is the issue, and I really think there is a logical flaw. Let me explain.
The "real" password in the .hccap file is 10 char long. The "real" password in the dic file is only 4 chars, and the rule in my rule file appends the remaining 6 chars. So the word in the wordlist is getting rejected (having only 4 chars) without even considering the additional extra characters that would eventually be appended (either at the beginning or at the end of the passphrase)!
What hashcat should really do is base this decision on the final output of the rule file result, not on the passphrase in the dictionary file alone.
Here is an example: I know your SSID password has the word "loving" in it, but I am creating some special rule file to append 3 more numbers (or characters) to that dictionary word... At the end, I will satisfy the over 8 chars for WPA, but right now hashcat is prematurely rejecting the entry in the dictionary file. Do you agree?
The "real" password in the .hccap file is 10 char long. The "real" password in the dic file is only 4 chars, and the rule in my rule file appends the remaining 6 chars. So the word in the wordlist is getting rejected (having only 4 chars) without even considering the additional extra characters that would eventually be appended (either at the beginning or at the end of the passphrase)!
What hashcat should really do is base this decision on the final output of the rule file result, not on the passphrase in the dictionary file alone.
Here is an example: I know your SSID password has the word "loving" in it, but I am creating some special rule file to append 3 more numbers (or characters) to that dictionary word... At the end, I will satisfy the over 8 chars for WPA, but right now hashcat is prematurely rejecting the entry in the dictionary file. Do you agree?