Change request: add parameter that for the first 4 digits about reaver-wps

[GoogleCodeExporter]

Temporarily created workaround by setting the correct p1 value index in
build_wps_pin() just before pin is created. (Not the prettiest solution)

set_p1(1, "4770"); //Use argv value here.
set_p1_index(1);

Original comment by [email protected] on 30 Dec 2011 at 1:17

[GoogleCodeExporter]

I would also find a parameter for the complete PIN very useful. 
I know of no utility that can simply display an AP's WPA password with a known 
WPS PIN. A useful way to recover a lost key since they can never be found in 
plain text once entered in either an AP or Windows (except Vista I think).

Correct me if I'm wrong and such tool exists!

In that regard a resume capability with logfile similar to besside-ng would be 
very handy. Obviously available in the government version.

Original comment by [email protected] on 31 Dec 2011 at 12:04

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

previous poster: it seems that an option for the complete pin has just been 
added

Original comment by [email protected] on 31 Dec 2011 at 3:36

[GoogleCodeExporter]

Only part of it has been added, you can only put the full code in, which is 
great for testing but you can't resume if you have to crash out of it after 
having the first 4 numbers.

Great addition though :)

Original comment by [email protected] on 1 Jan 2012 at 5:48

[GoogleCodeExporter]

I just got caught out by this so i've made the changes. I'm not a member of the 
project so i'm attaching the changed source to this comment.

New option is -p<first 4 digits> or --pin=<first 4 digits>

./reaver -i mon0 -b <whatever> -p <digits>

get the source, copy the changes to the src folder and rebuild. I got my source 
from the 1.2 tar.gz rather than svn so you'll want to do the same.

Original comment by [email protected] on 2 Jan 2012 at 12:36

Attachments:

• globule.c
• globule.h
• argsparser.c
• pins.c
• wpscrack.c

[GoogleCodeExporter]

For the moment i've forked reaver to solve this issue plus a couple marked as 
wont-fix as they in a pay only version.

There's a fix for this in my fork of reaver. It's based on reaver 1.2 and fixes 
this plus a couple of other issues.

http://code.google.com/p/theiver/downloads/list

Happy to unfork at some stage if we can start getting these sorts of things in 
the free version - otherwise i'm happy to add stuff in the fork.

Original comment by [email protected] on 2 Jan 2012 at 4:33

[GoogleCodeExporter]

I have also made a modified version with 2 new options:

-k    Turns on sequential order for 4 pin digits (0000, 0001, 0002 etc)
-s    Starting location

reaver -i mon0 -b 00:11:22:33:44:55 -k -s 1234   (would result in 1234, 1235, 
1236)

make distclean
./configure
make
make install

Original comment by [email protected] on 2 Jan 2012 at 11:20

Attachments:

• reaver-wps.zip

[GoogleCodeExporter]

We won't be adding a resume option to the official Reaver code as that is 
currently reserved for the commercial version (see issue #28).

@justin: Your updates conflict a bit with the latest SVN, but I'll be updating 
--pin to support either a partial 4 digit pin or a full 8 digit pin.

Original comment by [email protected] on 2 Jan 2012 at 1:12

[GoogleCodeExporter]

thanks I'll fix that now

Original comment by [email protected] on 2 Jan 2012 at 1:17

[GoogleCodeExporter]

No worries justin, adding support for partial 4 pin entries to the --pin option 
was a 2 line code change. Just checked in. :)

Original comment by [email protected] on 2 Jan 2012 at 1:26

• Changed state: Fixed

[GoogleCodeExporter]

That's great. I've taken your changes and removed mine for the pin.

Original comment by [email protected] on 2 Jan 2012 at 2:20