While running a configure script before compiling an application on CentOS Linux I received an error regarding libdaemon which caused the configure script to fail. Using YUM I was able to list the available packages that included libdaemon in the name, install one, and then move past that error in the configure script. Below I show how to list packages using YUM with libdaemon in the name and then show example output of installing libdaemon-devel which is the package needed by the configure script.
While running a configure script before compiling an application on CentOS Linux I received an error noting that libgdbm could not be found. Below I display the actual error output that interrupted the configure script, how the correct RPM package to resolve the error was located, and the output of installing the new package on CentOS Linux via YUM.
While running a configure script to eventually compile an application during testing on CentOS Linux I received an error stating that libexpat and/or libbsdxml could not be found. On CentOS you will only need to install libexpat-devel as shown in the below example following the output of the configure error and how we located what package installed libexpat via yum.
Not sure if Fortinet makes it impossible to find the FortiClient SSL VPN application for Mac OSX on purpose or not but it appears to be free for the simple client version so I wanted to provide a location to download the client easily. On Windows you can bring up Internet Explorer and make a SSL VPN connection easily but since IE is not available on OSX it is necessary to have the stand alone FortiClient SSL VPN application. Be careful if you are going to download the Fortinet FortiClient elsewhere as if it is anything other than the simple SSL VPN client it is really bloated.
So earlier today I noticed a discrepancy in traffic to question-defense.com and because of a previous incident I knew exactly where to look. Sure enough a similar attack had been performed which we are coining Search Engine Click Jacking. In this case we are sure that a single files permissions were left open and the attackers were able to write PHP into the file which caused traffic being referred to our site from many of the major search engines to be redirected to tenderloin.osa.pl. Our site is built using WordPress however any site built in PHP with incorrect permissions on any files are vulnerable to this type of attack. Below is more information about the attack, how to search for the attack, and a simple bash script that will remove the infected code from PHP files on your web site.