You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Run reaver, crack first 4 digits and let the program continue.
2. At some point it will try:
[+] Trying pin 47704244
[!] WARNING: Receive timeout occurred
However, this is the correct pin, but due to a timeout, it is skipped, not
repeated?
What is the expected output? What do you see instead?
I see that it continues to crack other pins, but not repeating the correct one.
I believe it's supposed to retry the pins that encountered a timeout.
What version of the product are you using? On what operating system?
latest svn checkout (v16)
Please provide any additional information below.
Original issue reported on code.google.com by stefanen...@gmail.com on 30 Dec 2011 at 12:30
The text was updated successfully, but these errors were encountered:
I see the bug. The do_wps_exchange function tries to automatically identify if
the AP properly sends WSC NACK messages on failure (some don't, they just stop
responding...). Unfortunately I'm not saving this state across calls to
do_wps_exchange, so some timeouts are getting treated as NACKs when they
shouldn't be.
A fix is checked in, I would appreciate verification if possible. A work around
is to specify '--nack' on the command line, which tells Reaver that the AP
always responds with a NACK message on failure (most do).
Original comment by cheff...@tacnetsol.com on 30 Dec 2011 at 12:27
Original issue reported on code.google.com by
stefanen...@gmail.com
on 30 Dec 2011 at 12:30The text was updated successfully, but these errors were encountered: