Closed feitoi closed 3 days ago
After many observations, if receive deauth request before M3 then ends WPS transaction sending WSC_NACK and restart the attempt. If receive deauth request after M3/M5 then waiting timeout and store the count value in .wpc file. If after 10 times not received any NACK then it can consider router sends deauth request instead of NACK. If receive NACK then store -1 that represents router sends NACK and ignore deauth request treatment.
is there a specific reason you're closing this ?
I've already analyzed several situations with deauth request, it appears after
Sending identity response
,Sending M2 message
,Sending M4 message
,Sending M6 message
, sometimes also receiveWSC NACK
after receivedeauth request
. Later I tested with routers with PIN already cracked and noticed that some routers are not sending WSC NACK instead of deauth request. With this knowledge I think it is possible to treat deauth request after Sending M4 message or Sending M6 message and got timeout as WSC NACK with new option -D to treatdeauth request
asWSC NACK
see an example with modified reaver with message count and PIN not cracked yet:
Example with half PIN:
Example with full PIN:
see an example without PIN: