Closed GoogleCodeExporter closed 8 years ago
If you are testing this on your own router, you should have no problems
connecting to it, no? Unless I'm missing something...
Original comment by philippe...@hotmail.com
on 5 Jan 2012 at 4:14
It has been found that some APs don't return the existing WPA key, but instead
generate a new one that is returned to the registrar (presumably so that the
registrar can then configure the AP with this new random WPA key). This is not
something that Reaver can control AFAIK (there is an option in the WPS exchange
that is supposed to tell the AP to not do this, but some seem to ignore it).
This could be the issue in your case; of course, that WPA key could also be the
correct one, there's no way for me to know. Either way, Reaver is functioning
properly.
Original comment by cheff...@tacnetsol.com
on 5 Jan 2012 at 4:28
Original issue reported on code.google.com by
burakozy...@gmail.com
on 5 Jan 2012 at 4:11