Since we know our mac and our anonce (both are part of the authentication process and the calculation of the keys), we can start to crack the hash without the M1 of the legitimate ap.ġ) This attack works only on the message_pair M1/M2. Transmitted m1/received appropriate m2.: 343/719Īnd the regular messages from a real ap connected to a client: Wlandump-ng will show us this (using the -s xx option): So we receive a valid M2, calculated from an entry in his wpa_nf. Wlandump-ng accepts and sends a M1 (we are just friendly and give the client what he wants).Īfter receiving this M1 the client sends us his M2, because he can't resist us. Using the defaults, a client probes every ap which has an entry in his wpa_nf.Ī stupid client also probes his 5GHz ap on 2.4GHz!

If the M3 is ok the client acknowledges and sends the M4 (that means the ap is authenticated) If the M2 is ok, the ap acknowledges and sends the M3 (that means the client is authenticated) The ap acknowledges and sends an authentication response followed by the M1 The ap responds to the authentication request The clients sends an authentication request The authentication process is very simple to understand:

This is an attempt to get the M2 of the client (and that works perfect). In that case, we are the access point (ap) which the client expected to see. Well, answering every probe request, makes it possible that a client will try to connect to us.

Wpa2 wordlist 2017