Save Session Per BSSID

[GoogleCodeExporter]

Firstly thank you very much for Reaver !!  You have shown me that my wireless 
router was insecure and I can now take steps to secure it further :o)

Can you please add a feature request that when a user has to stop half way 
through a test that Reaver stores the last position as it does now but with the 
added feature that this is based on BSSID.

This way if a user wants to finish early on testing router "A" and test a 
different router "B" they do not lose position on the first router "A" when 
they return to it at a later date ?

At the moment if a user has to switch jobs they lose the first saved position 
on router "A" even though the test is being performed on a different router and 
BSSID.  It should be based on BSSID as they may be confusion with AP's being 
named the same "Netgear" for example !!

When a user starts Reaver it should check through the saved files and see if it 
already has a job with that same BSSID.  The user should then be presented with 
the option to use it or start again.

Thank you.

Original issue reported on code.google.com by keyfo...@veryrealemail.com on 22 Jan 2012 at 2:15

[GoogleCodeExporter]

Sorry ,for some reason this seems to have been marked as "Defect" when it 
clearly isn't, I am certain I marked it as "Enhancement".

I don't seem to be able to edit it....sorry.  :o(

Original comment by keyfo...@veryrealemail.com on 22 Jan 2012 at 2:53

[GoogleCodeExporter]

This is how reaver already saves session data. Session files are named 
<bssid>.wpc, and are automatically stored in /usr/local/etc/reaver. When you 
start reaver against <bssid>, reaver looks for a <bssid>.wpc file, and if it 
exists it will ask you if you want to resume.

If you are using the --session=<file> option, then reaver will save the session 
to whatever file you specify. If you use the same file name for multiple APs, 
then session data from older APs will be overwritten. If you don't specify the 
--session option, then reaver will auto-save the session data as described 
above.

Original comment by cheff...@tacnetsol.com on 22 Jan 2012 at 3:03

• Changed state: Invalid

[GoogleCodeExporter]

So it does !! :o)

I am sorry and I apologise for not noticing that !  All I can say in my defense 
is "great minds" and all that !

I am sorry for wasting your time.

Can I make a small request that when Reaver asks the user if they want to 
restore the session that it includes the BSSID ?  Something like...

Do you want to restore the session for 00:11:22:33:44:55 ?

Maybe even add the date and time ?

This way new users (like myself) will realise that Reaver has indeed stored the 
session for that particular BSSID.  I wrongly assumed that Reaver was asking to 
restore the last session from a different AP, the clarification of the BSSID in 
the restore question will eliminate that.

Thank you.

Original comment by keyfo...@veryrealemail.com on 22 Jan 2012 at 4:11

[GoogleCodeExporter]

Done. :)

Original comment by cheff...@tacnetsol.com on 22 Jan 2012 at 6:57

[GoogleCodeExporter]

Wow fast ! :o)

That's very kind of you, thank you very much.

Original comment by keyfo...@veryrealemail.com on 22 Jan 2012 at 7:11

[GoogleCodeExporter]

Thank you for Reaver !!
I would like to use this thread to ask if this path '/usr/local/etc/reaver' is 
the same in 1.4 release?
Last week i've tried 1.3 and restoring session over same BSSID was automatic 
and successful. Since yesterday i am trying 1.4, but automatic session 
restoring somehow is not working. I am pretty sure that i am not doing 
something right, but i dont know what. 
I checked if in the above mentioned path is stored files <BSSID>.wrc, but i was 
surprised to find that there is no '/reaver' in '/usr/local/etc/'.

I am using BT5 live dvd.

Thanks in advance and best regards!

Original comment by nico...@gmail.com on 25 Jan 2012 at 8:29

[GoogleCodeExporter]

1.3 probably saved the sessions in the /etc/reaver directory. You can copy all 
of the wpc files from there to /usr/local/etc/reaver, or specify the path 
explicitly with --session.

Original comment by cheff...@tacnetsol.com on 25 Jan 2012 at 1:00

[GoogleCodeExporter]

Thank you! I will try that :) :respect:

Original comment by nico...@gmail.com on 25 Jan 2012 at 1:13

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

reaver Starting from 90%, when up to 99.99% reiterates the same code to 
infinity What the solution to this problem???? Please note I wiped files stored 
inside /usr/local/etc/reaver. Please advise me

Original comment by aliabd...@gmail.com on 26 Jan 2013 at 10:36

[GoogleCodeExporter]

The starting from 90% and getting stuck repeating the same pin (12349982) 
problem is pretty common, a suggested solution can be found here: 
http://code.google.com/p/reaver-wps/issues/detail?id=195

Whether it works or not I can't say. However I am currently testing it and will 
comment again if it works.

Original comment by Illumina...@gmail.com on 12 Mar 2013 at 10:16

[GoogleCodeExporter]

I wish there was an option to start scanning fresh from any number of your 
choice.  Sometimes while using Xiaopan in VMware I will get a problem with 
Inflator and other apps scanning.  It will scan for a the preset amount of time 
but will return Zero finds.  Disconnecting and unplugging the usb Wi-Fi a few 
times sometimes resolves it.  Unfortunately, often times no matter how many 
times I try I'm left with no option but to exit the Xiaopan instead of simply 
suspending it.  When you do that you lose your previous setting.  Very 
fruastrating when you've spent 8 hours scanning at the number count is 
750,00,000+.  You have to start all over again.  There is an option to specifiy 
a single number but it doesn't increment, it just keeps trying the same number 
over and over again.  Also studying the wpc file doesn't reveal a simple method 
of creating my own file to fake a resume later on.

Original comment by Granta1...@gmail.com on 16 Apr 2013 at 10:04

[GoogleCodeExporter]

I am using Reaver on Ubuntu 13.10 and the Reaver was running pretty good. It 
completed 60 % and I saved session by ^C. Now I am not able to restore it. When 
I typed the command again, it started just a new session. I tried in 
/usr/local/etc/ and in /etc/, but I cannot see any Reaver folder. It was 
running for about 14 hours ( yes I was attempting from a good distance ) and 
now it wants to start new. I tried several times saving sessions after leaving 
it run for a while, but it never asked for or restored a saved session. 

Original comment by comrade....@gmail.com on 29 Apr 2014 at 11:25