06-22-2019, 06:30 PM
(06-22-2019, 05:32 PM)ZerBea Wrote: Yes, cap file and hccapx is ok:
$ hcxpcaptool -o test.hccapx test.cap
reading from test.cap
summary:
file name........................: test.cap
file type........................: pcap 2.4
file hardware information........: unknown
file os information..............: unknown
file application information.....: unknown
network type.....................: DLT_IEEE802_11 (105)
endianness.......................: little endian
read errors......................: flawless
packets inside...................: 9884
skipped packets (damaged)........: 0
packets with GPS data............: 0
packets with FCS.................: 0
beacons (total)..................: 1
probe responses..................: 37
association requests.............: 5
association responses............: 4
authentications (OPEN SYSTEM)....: 11
authentications (BROADCOM).......: 4
deauthentications................: 4605
action packets...................: 47
EAPOL packets (total)............: 43
EAPOL packets (WPA2).............: 43
best handshakes..................: 2 (ap-less: 0)
2 handshake(s) written to test.hccapx
I'm able to get the correct PSK (6*******) from both clients running
hcxpsktool --wpskeys | hashcat -m 2500 test.hccapx
within a few seconds. That worked also on your attached test8.hccapx
BTW:
How did you captured the handshake?
4605 deauthentications to get a single handshake looks a little bit oversized.
used fluxion to get the handshake
[/url]https://github.com/FluxionNetwork/fluxion
[url=https://github.com/FluxionNetwork/fluxion]