I was building a tool called Sipcrack today from source and ran into some problems. The platform I was using was ubuntu 10.04 LTS but if you are getting this error on any Ubuntu platform the solution is most likely going to be the same.
I have recently gotten a macbook pro to play around with so my next few articles will most likely cover getting the tools and such the way I want them on the mac book pro. The first thing I discovered is that many of the command line tools which I use every day such as nmap are available in the macports package which is a package management system similar to what I was used to in Linux.
I will details the steps I had to take to get macports installed:
Earlier I was compiling the coreutils application on CentOS Linux and ran into an issue after using the “make” command. At first I was confused because I wasn’t doing anything complex but then I realized that I had simply mistyped an environment variable I had previously set. Below I describe the actual error, what was mistyped, and how I resolved the problem.
Error Building Pyrit On CentOS: cpyrit/_cpyrit_cpu.c:26:18: error: pcap.h: No such file or directory
When building pyrit, which is an application that uses GPU power to run dictionary attacks against WPA handshake captures, on CentOS Linux I ran into an error. The error was related to the pcap.h library which was not found by the pyrit setup.py python script. Resolving the problem is easy by simply installing the libpcap-devel RPM package using the yum package manager. Below I display more output surrounding the error, the log showing the libpcap-devel package installation, and finally the successful build of pyrit on CentOS Linux.
When compiling an application called pyrit on a new CentOS Linux server I ran into an issue with some libraries. Pyrit is an application used to perform dictionary attacks against WPA handshakes and can be really useful for security auditing. The error below is easily resolved on any version of Linux by simply installing the glibc-devel RPM package. Below I display the error in detail as well as how to resolve the error on CentOS by installing the glibc-devel RPM using the Yum package manager.