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.
PBNJ is made ip of two commands which are scanpbnj and outputpbnj. The manpages for both scanpbnj and outputpbnj are located in collapsed tables at the bottom of this post in case you want more details. When you run scanpbnj it technically a script that runs nmap and dumps the results to a database. The scanpbnj command will store results in various database formats including CSV, MySQL, PostgreSQL, and SQLite. Once the results are stored you can pull the results from the database using outputpbnj which can output report style results in CSV format, tab delimited format, or HTML format. Continue reading below for more details regarding outputpbnj and scanpbnj on Backtrack Linux 5 r2.
While playing around with pbnj or scanpbnj on Backtrack just a little bit ago I received an error when attempting to have scanpbnj output results to a CSV file. The error received is easily resolved by installing a single package on Backtrack. Below the error is described in more detail along with details about how to install the package that resolves the error message.
This afternoon I was using PGAdmin and needed to export some data from a query I had run but realized I wasn’t even sure if PGAdmin had this capability. Typically I would export data using the PSQL command line but since I was already working in PGAdmin I wanted to try and figure out if the capability existed and if so how to do it. After some playing around I was able to figure out how to export PGAdmin data to a CSV (Comma Separated Value) format that would be Microsoft Excel friendly. Follow the directions below to export PGAdmin data to a .CSV file to open in MS Excel.
A client of mine still has a computer running Microsoft Outlook Express and they wanted me to import the address book contacts into their Yahoo Mail account. At first I was a little worried that Yahoo Mail may no longer support the format of Outlook Express address book contacts but then I remembered that you can export contacts into a CSV (Comma Separated Values) file which means I could manipulate the data if it was not supported. Yahoo Mail says that it supports import from Outlook but it doesn’t specify Outlook Express. I assume the format between Outlook and Outlook Express must be similar because Yahoo Mail did import the exported contacts from Outlook Express. Below I describe how to export Outlook Express contacts and then import those contacts into Yahoo Mail. Follow the instructions below that are broken into two parts which include exporting the contacts using Outlook Express and then importing the contacts using the Yahoo Mail web interface.