No problem, you're welcome.
BTW:
To test this weak point you can do this steps:
Take a look at your stored WiFi NETWORKs of your smart phone.
Add them to an essid.list.
Look for a free WiFi channel (for the example we assume channel 9 is free).
Run hcxdumptool with option essidlist and active_beacon:
Disable WiFi and enable WiFi on your smart phone.
Wait a while (as long as the CLIENT respond, > 10 min).
You should retrieve valid handshakes (M1M2 challenge) for every stored NETWORK of your smart phone's NETWORK list. In that case, the smart phone is vulnerable to this attack vector.
BTW:
To test this weak point you can do this steps:
Take a look at your stored WiFi NETWORKs of your smart phone.
Add them to an essid.list.
Look for a free WiFi channel (for the example we assume channel 9 is free).
Run hcxdumptool with option essidlist and active_beacon:
Code:
$ sudo hcxdumptool -i YOUR_INTERFACE -c 9 --enable_status=31 -o dump.pcapng --essidlist=essid.list --active_beacon --stop_client_m2_attacks=1000Wait a while (as long as the CLIENT respond, > 10 min).
You should retrieve valid handshakes (M1M2 challenge) for every stored NETWORK of your smart phone's NETWORK list. In that case, the smart phone is vulnerable to this attack vector.