duplicate networks capture not saved

[GoogleCodeExporter]

What steps will reproduce the problem?
1. find two wireless networks with same essid
2. run scrypt
3. capture 2 handshakes with same essid

What is the expected output? What do you see instead?
when two identitical essid found and handshake captures occured it says will 
not save second capture becouse there is with this name. Need to add MAC?

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

Please provide any additional information below.

Original issue reported on code.google.com by usmi...@gmail.com on 9 Mar 2011 at 11:49

[GoogleCodeExporter]

Is there any way you could copy and paste the output from the program?  
Specifically the part that says "will not save second capture..."? This would 
help me a whole lot, as I am unable to reproduce this bug.

I started two access points with the same ESSID, and then connected to the 
first one ("AP #1") while listening for handshakes on the second ("AP #2").  I 
did not have any conflicts.  When I finally connected to the second on ("AP 
#2"), I caught the handshake as expected.  Could you walk me through the steps 
you took to produce this bug?

Original comment by der...@gmail.com on 10 Mar 2011 at 9:04

[GoogleCodeExporter]

as i remember
1 AP "linksys" WPA
2 AP "linksys" WPA
i start wifite.py
on wlan0 -> mon0
tell all networks to scan
set dictionary to none
get capture from 1st AP  save it on directory
when get second capture i received message that i have
already linksys.cap file and will not save it
so will need to capture it again
so i renamed first one adding MAC address to it
run again wifite.py and get second capture
but if it is possible it can be done via script
if i go to same place i will reproduce conditions for this situation and will 
save it
as images and log files

the other idea is to prepare wifite for wardriving:
for example warmode:
if found AP try to:
WEP - fake auth and atack - if chances for recieve 9k packets  in next 10 min - 
ding ding (audio signal)
WPA - capture handshake and if suceed - ding (audio)
and repeat investigating AP for strong signal

Original comment by usmi...@gmail.com on 10 Mar 2011 at 9:25

[GoogleCodeExporter]

Oh! I understand now.

Yes, I should change Wifite to save the files "[ESSID][BSSID].cap" so that 
there are not collisions.  I will make a note of this and will make the changes 
later this week.

Regarding your wardriving idea:

I *could* make a wardriving version of Wifite... A wardriving verison would 
have to be separate from the current version (more automated), but this is a 
very good idea.  I will look into it and try to come up with more ideas for it. 

I will post comments if/when I get started on a wardriving version of wifite.  
Thanks!

Original comment by der...@gmail.com on 11 Mar 2011 at 2:08

• Changed state: Accepted

[GoogleCodeExporter]

few more ideas:
+ add bateri level indicator (i use it as console and do not have warning on 
low battery - airodump and etc has bateri meter)
+ when found network - add description - ding ding ding signal - where found etc
+ add rainbow table support (cowpatty rainbow table directory) for standart 
wifiter version
+ add more WEP attacks - hop mode are few AP mode ...
+ wardriving mode - save every 5 minutes - recovery can be done when returning 
to point - if battery is low
+ war mode - add prefered networks - for example 1000 most popular SSID to use 
with rainbow tables for WPA
+ war mode - get router adress, check for name and search for default pass from 
list - test and if suceed - ding ding

i am ready to help with programing testing and all needed :)

Original comment by usmi...@gmail.com on 11 Mar 2011 at 11:38