Reaver won't resume session in Kali 1.0

[GoogleCodeExporter]

A few things to consider before submitting an issue:

0. We write documentation for a reason, if you have not read it and are
having problems with Reaver these pages are required reading before
submitting an issue:
http://code.google.com/p/reaver-wps/wiki/HintsAndTips
http://code.google.com/p/reaver-wps/wiki/README
http://code.google.com/p/reaver-wps/wiki/FAQ
http://code.google.com/p/reaver-wps/wiki/SupportedWirelessDrivers
1. Reaver will only work if your card is in monitor mode.  If you do not
know what monitor mode is then you should learn more about 802.11 hacking
in linux before using Reaver.
2. Using Reaver against access points you do not own or have permission to
attack is illegal.  If you cannot answer basic questions (i.e. model
number, distance away, etc) about the device you are attacking then do not
post your issue here.  We will not help you break the law.
3. Please look through issues that have already been posted and make sure
your question has not already been asked here: http://code.google.com/p
/reaver-wps/issues/list
4. Often times we need packet captures of mon0 while Reaver is running to
troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap).  Issue
reports with pcap files attached will receive more serious consideration.

Answer the following questions for every issue submitted:

0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)
Reaver 1.4

1. What operating system are you using (Linux is the only supported OS)?
Kali Linux

2. Is your wireless card in monitor mode (yes/no)?
Yes

3. What is the signal strength of the Access Point you are trying to crack?
-50? Not sure if this is what you mean

4. What is the manufacturer and model # of the device you are trying to
crack?
Sagem Skybox

5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -c1 -b 00:11:22:33:44:55 -vv -S -N -L -x361 -d 10 -r 20:361 -T 1 
-l 600

6. Please describe what you think the issue is.
I am unsure but I have tried placing an edited 001122334455.wpc file into 
/usr/local/etc/reaver (had to make folder) as stated in Issue 233 but with no 
success. I am booting from a USB using Kali Live but I am not shutting down so 
surely I should be able to resume?

7. Paste the output from Reaver below.
I am unable to as I am back on windows now. The Reaver output doesn't say 
anything out of the ordinary. It just says session saved after ctrl+c (if I am 
lucky) then when I input the same bssid it starts from the beginning again 
regardless.

Thanks, hope to get this one sorted!

Original issue reported on code.google.com by mrvarial...@hotmail.com on 16 Mar 2013 at 1:13

[GoogleCodeExporter]

Nvm, I have solved the issue. 
For anyone else encountering it any edited 1a2b3c4d5e6f.wpc session file needs 
to be in root to work and I added -s 1a2b3c4d5e6f.wpc to the end of the reaver 
command to save the current session file, I then edited the first line to the 
pin line i was upto in reaver, then ran the same reaver command again 
(including the -s 1a2b3c4d5e6f.wpc) and it finally said it had recovered the 
previous session! Should hopefully be able to do it now without the editing of 
the wpc file.

Original comment by mrvarial...@hotmail.com on 16 Mar 2013 at 1:58

[GoogleCodeExporter]

your reaver -i mon0 -c1 -b 00:11:22:33:44:55 -vv -S -N -L -x361 -d 10 -r 20:361 
-T 1 -l 600
flag -a where is ? 

Original comment by deltomaf...@gmail.com on 21 Apr 2013 at 4:04

[GoogleCodeExporter]

Creating /etc/reaver will fix reaver resume issue. Files will be saved back in 
the reaver folder. This also fixes wash. 

mkdir /etc/reaver

Original comment by Rre...@gmail.com on 28 Jul 2013 at 8:04