search

bngmc / reaver-wps

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

After our reviews... #124

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
According to our test, it seems that reaver 1.3 is still unstable and hard to 
crack a PIN code when the SNR is low (although it supported saving session in 
version 1.3). So, reaver1.3 is still NOT to be recommanded.
We hope the author of Reaver could develops a stable version. Thank you.

The Bugs we found during our tests:
*While we use -p 12345678, the log shows Trying pin 12345670 (is that a bug?)
*In some case, we found that the router will reply an incurrent PIN code but 
reaver said that it is a current one and then suspended the progress. The PIN 
code is random. (Tenda W150M, bug fixed after reset the router.)
*In some case, the WPA-PSK is incurrent and random.(Tenda W150M) But on the 
other hand, it gave me a current code in TP-LINK 740n.
*If you type MAC address without ":", it will not be able to work on it.

Lingxi @ WIFIBETA
2012/01/11

Original issue reported on code.google.com by lolisda...@gmail.com on 11 Jan 2012 at 1:36

GoogleCodeExporter commented 8 years ago 
 "it seems that reaver 1.3 is still unstable and hard to crack a PIN code when the SNR is low"

This is an active attack, and will not work well if you have a poor signal from 
the target AP. Unfortunately that is something that is beyond my control.

 "While we use -p 12345678, the log shows Trying pin 12345670 (is that a bug?)"

The pin 12345678 is not a valid pin. The last digit is a checksum of the first 
7 digits. Reaver changed the pin to have the correct checksum.

 "In some case, we found that the router will reply an incurrent PIN code but reaver said that it is a current one"

This is a duplicate of issue 16. It only appeared to have manifested itself in 
when a receive timeout occurred at a certain point. It has already been fixed.

 "In some case, the WPA-PSK is incurrent and random.(Tenda W150M)"

This is a duplicate of issue 25. Some APs generate random WPA keys rather than 
returning the current WPA key. This is an AP-specific issue and not something 
that I have control over.

 "If you type MAC address without ":", it will not be able to work on it."

Correct. If you don't provide a properly formatted MAC address, Reaver won't 
know how to parse it; I believe you'll find this is true for most wireless 
tools. The colon-separated format is the standard format for MAC addresses in 
Linux, and is what Reaver expects.

Original comment by cheff...@tacnetsol.com on 11 Jan 2012 at 4:36