When using Reaver(I have the newest version), I have noticed that the WPS pin
attempt often gets 'hung up' on a pin, trying it several times in a row. This
occurs no matter how close I am to my AP, despite being associated, and using
the every combination of options to speed up the process. Now that being said,
I have noticed that if I interrupt the attack and restart it(ctr-c), the
hang-up often clears right up- moving on to the next pin attempt. I believe
this has something to do with un-associating and re-associating(using fakeauth)
with the AP.
Building in a feature whereby Reaver automatically interrupts the attack after
multiple attempts of the same WPS pin in order to un-associate and re-assocaite
to the AP(using fakeauth) might be able to increase the speed at which Reaver
is able to complete its attack.
-The Drizzler
Original issue reported on code.google.com by garciama...@gmail.com on 26 Oct 2013 at 11:44
Original issue reported on code.google.com by
garciama...@gmail.com
on 26 Oct 2013 at 11:44