seteve / reaver-wps

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

Lost saved status after updating to r80 #116

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I had 77.56% completed, and the process was going very slow.  I read through 
the current issues and decided to try checking out the latest revision (r80).  
When I started it up again, I was not given the option to resume the recovery.  
Is all of my progress lost?

Original issue reported on code.google.com by magnum9...@gmail.com on 9 Jan 2012 at 5:58

GoogleCodeExporter commented 8 years ago
It should not be, but I'm pretty sure I know what the problem is.

Reaver is likely looking in a different directory for the session files. 
Previous versions looked in /etc/reaver, while more recent SVN builds are 
probably looking in /usr/local/etc/reaver (may vary depending on your system). 
You can use the --session option to explicitly specify the path to your session 
file:

# reaver -i mon0 -b <bssid> -vv --session=/etc/reaver/<bssid>.wpc

Original comment by cheff...@tacnetsol.com on 9 Jan 2012 at 6:12