After getting home from an awesome game, I was in the mood to write some more Perl! I found a few more things during the day that I wondered how I was able to go without writing them already. The first is intersection and the second is union. They do exactly what you think they do and keep things very simple, keeping with the UNIX way. "Do one thing, do it well!" Anyways, perhaps I'm just tired but I wasn't aware of a tool that provided the functionality I needed. Therefore, I did what I always do, rolled my own.

$ cat file1 
127.0.0.1
127.0.0.2
127.0.0.3
$ cat file2 
127.0.1.1
127.0.2.1
127.0.3.1
127.0.0.1
$ ./intersect file1 file2
127.0.0.1
$ ./union file1 file2 
127.0.0.1
127.0.0.2
127.0.0.3
127.0.1.1
127.0.2.1
127.0.3.1

The scripts can be found at:
http://spl0it.org/files/intersect.pl
http://spl0it.org/files/union.pl

Let me know what you think.

Regards,
Jabra

So I noticed there is a free services at SkyHook Wireless to get the physical location of wireless router from its MAC address (BSSID)s Therefore, I decided to write up a Perl script since I saw that no one had done it yet.

$ ./bssid-location.pl AABBCCDDEEFF
Longitude: 12.4225458
Latitude: 41.850425

The script can be found here.

Regards,
Jabra

These are three images using some software that I'm finishing up. For now, it lacks in documentation, but I guess a picture is worth a 1000 words!

The more important image is the second, due to the fact it demonstrates what makes the first image. The data is based on extracting information from Kismet and storing it into a database. Once the data is stored, the user is able to generate KML files that can be opened in GoogleEarth.


Let me know what you think.

Regards,
Jabra

At the end of the day I was preparing my things to go home, but I needed to schedule a few scans to execute over night. In the past I have used cron, but it occurred to me that cron isn't the best tool for setting up a single event that does not reoccur. The reason is it isn't as quick as something that can be setup on the command-line. Cron requires you to use "crontab -e" or something. I quickly considered some Perl, but being lazy and short on time I needed another option. Then it occurred to me that I had forgotten about at.

So I reviewed the man page and setup a few tasks and called it a night.

at -f scan.sh 1:00 tomorrow
at -f scan2.sh 2:00 tuesday
at -f scan3.sh 3:00 september 16

Regards,
Jabra