Enhancement Request: Collate AP data for 'optimised' settings

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Allow users the option to send data to yourselves on the first three values 
of the MAC address of attacked AP's with the variables used to attack that AP 
and how successfull those attacks have been.

2.
3.

What is the expected output? What do you see instead?

The first 3 variables of the MAC address of an attacked AP show the 
manufacturer and sometimes the model.  If successful attacks are collated and 
uploaded for other users to utilise this would optimise attack strategy.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by pinsb...@gmail.com on 5 Jan 2012 at 1:33

[GoogleCodeExporter]

The program shouldn't call home to send data without asking for user permission 
though.

Original comment by b1957...@nwldx.com on 5 Jan 2012 at 3:39

[GoogleCodeExporter]

That's why the first line said "Allow the users the option...."

Original comment by pinsb...@gmail.com on 5 Jan 2012 at 7:21

[GoogleCodeExporter]

Issue 96 has been merged into this issue.

Original comment by cheff...@tacnetsol.com on 6 Jan 2012 at 3:52

[GoogleCodeExporter]

We're looking in to having an open source database where users can submit 
settings and download the DB to be used with Reaver.

Original comment by cheff...@tacnetsol.com on 6 Jan 2012 at 3:53

• Added labels: Priority-Triage, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Perfect, thanks guys.

Original comment by pinsb...@gmail.com on 6 Jan 2012 at 4:18

[GoogleCodeExporter]

Backtrack 5v2 64bit
Atheros mini PCI ath9k
reaver v 1.4 r68
AP NetgearWNR 2000v2 E0:91:F5:60:xx:xx
Airodump signal -69 distance aprox 40m through window

command used:
reaver -i mon0 -b netgearsmacaddr -L -c 1 -a -d 0.2 -S -vv

-L was important because the AP locks for a random time but then continous 
while reaver running, when reaver has found the first four digit it does not 
lock anymore until the end.

-c was also important because the channel does not switch everytime during 
lockstate but you have to observe the output and check the channel again 
sometimes.

Original comment by patricks...@gmail.com on 6 Jan 2012 at 5:07