Hi all,
This is an odd one that may not be a reaver issue, but reaver is the only app
doing anything odd like this.
Basically, I setup reaver as such, simple enough:
reaver -b <MAC ADDR> -i mon0 -vv -S -c 1
I open a term and periodically check the status of how many pins we've tried
with this:
head /etc/reaver/XX:XX:XX:XX:XX:XX.wpc
So I had to reboot, ran head then stopped and rebooted. PIN count wass at 4876
last check. After reboot, restarted reaver, same cmd line and head cmd to
monitor it.
Noticed reaver was making progress, but file wasn't updating.
Upon investigating, the .wpc file it was using was in /usr/local/etc/reaver and
was only at pin ~3800.
The fact these files are both same MAC filename, and both are at fairly high
PINs tells me reaver is working both somehow between restarts.
Very wierd, and potentially a huge waste of time.
Is there some ENV var that maybe messing with this or something?
Confused. Thx.
Original issue reported on code.google.com by mathieso...@gmail.com on 29 Jul 2013 at 5:20
Original issue reported on code.google.com by
mathieso...@gmail.com
on 29 Jul 2013 at 5:20