The other day I had a wireless network packet capture file saved as a .cap file. The ESSID that was displaying via normal aircrack-ng output of the WPA/WPA2 wireless packet capture lead me to believe there was at least one space included in the beginning of the ESSID and likely after the ESSID since it was not processing properly using oclHashcat-plus. I had never run into this before so wasn’t exactly sure the easiest way to figure out the number of spaces so I posed the question in the Freenode aircrack-ng IRC channel and got a couple responses which are noted below as well as instructions following the clearest solution.
I recently aquired a new GPS device for use with programs like Kismet and Airodump-ng. Its been a while since I have used GPS devices in Linux and back then they were serial devices. The BU-353 dvice is a USB device so I had to figure out how to get it going.