h-eibot / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

WPS and WPS Pin #371

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Doing some Reaver (v.14) testing against my UK Virgin Media WPS enabled AP - 
and have encountered some unexpected results.

Attachment 1 (available on request): wps_pin_en

Shows WPS and WPS PIN enabled on the AP.
Shows the WPS PIN.
Reaver input where I've "guessed" the PIN number.
Reaver output successfully retrieving the WPA-PSK key.

Attachment 2 (available on request): wps_pin_dis

Shows WPS enabled - but WPS PIN disabled on the AP.
Greyed out WPS PIN.
Reaver input where I've "guessed" the PIN number.
Reaver output unable to retrieve the WPA-PSK key - despite knowing I've 
successfully "guessed" the WPS PIN.

So I guess my question is;

Are both WPS and WPS PIN functionality required to be enabled for a Reaver 
attack to work?

Why is this important? If WPS is enabled on the AP - but the WPS PIN option is 
disabled - will the attack vector fail?

Cheers

Chris.

Original issue reported on code.google.com by r8415...@gmail.com on 10 Aug 2012 at 5:25