Hi hulley.
wlanhcxcat is not like hashcat. It is very, very slow. Main purpose is to verify an existing(!) PMK while another cracker is running.
A typical application example is:
hashcat is running und you want to check an existing PMK (debug purpose) or you wnat to retrieve the internal calculated MD5-64 checksum for this hashrecord
$ wlanhcxcat -i test.hccapx -w pmklist
started at 06:17:00 to test 788 records
output is the same like hashcat potfile if the PMK is verifed.
If Atom releases a new hashcat version I compare new hashcat results (potfile) with the output of wlanhcxcat to detect errors and report issues.
wlanhcxcat is not like hashcat. It is very, very slow. Main purpose is to verify an existing(!) PMK while another cracker is running.
A typical application example is:
hashcat is running und you want to check an existing PMK (debug purpose) or you wnat to retrieve the internal calculated MD5-64 checksum for this hashrecord
$ wlanhcxcat -i test.hccapx -w pmklist
started at 06:17:00 to test 788 records
output is the same like hashcat potfile if the PMK is verifed.
If Atom releases a new hashcat version I compare new hashcat results (potfile) with the output of wlanhcxcat to detect errors and report issues.