snowflakekiller / wifite

Automatically exported from code.google.com/p/wifite
GNU General Public License v2.0
0 stars 0 forks source link

BSSID in log / SQLite log #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
After using wifite a few times, I had a couple features I'd love to have.  
 * Firstly, since I sometimes test multiple APs with the same ESSID, it would be nice to have the BSSID stores in the log file as well.  
 * Second, after having a large number of results, I was thinking an sqlite log file might provide more advanced organization, and if it was a single table, simple queries on the command line wouldn't be to difficult for those unfamiliar with sql.

Original issue reported on code.google.com by bettse@gmail.com on 10 Mar 2011 at 7:19

GoogleCodeExporter commented 9 years ago
I just realized I screwed up on setting the type, this should be Enhancement, 
not Defect.

Original comment by bettse@gmail.com on 10 Mar 2011 at 7:20

GoogleCodeExporter commented 9 years ago
Changed to Enhancement.

Thanks for the feature requests.  Storing the BSSID in the log file makes 
sense, so that will probably get added quickly.  I don't know how to use SQL 
with python yet, so a sql database is probably not going to happen for a while.

Original comment by der...@gmail.com on 10 Mar 2011 at 7:34

GoogleCodeExporter commented 9 years ago
I've tinkered with python and sql; would you be open to a patch if I could get 
one going?

Original comment by bettse@gmail.com on 10 Mar 2011 at 7:35

GoogleCodeExporter commented 9 years ago
Sure, I just committed r67 (added the BSSID to log.txt printout, also tried to 
fix issue 39).

Feel free to write a patch for r67 and then link to it from the comments, or 
email it to me via gmail.  I can run a diff, check the changes, and then commit 
you patch.

I'm busy this week, so feel free to take your time with writing the patch.  

Thanks for the help!

Original comment by der...@gmail.com on 10 Mar 2011 at 8:58

GoogleCodeExporter commented 9 years ago
Here is my first treatment of it.  I went for dead simple.  Any keys that are 
collected are added to a log.db, to a table called 'log'.  

I'm considering writing a further patch to take all the various status lines 
that are printed to the command line and put them into a 'status' table, but 
since most of those are print statements, I wanted to make sure this patch was 
up to snuff first.

Original comment by bettse@gmail.com on 10 Mar 2011 at 11:22

Attachments:

GoogleCodeExporter commented 9 years ago
Closing as I added this patch in r70

Original comment by bettse@gmail.com on 8 Apr 2011 at 2:14