Tuesday, December 23, 2014

Thursday, September 25, 2014

How to identify if your bash shell is vulnerable to Bash Code Injection Vulnerability (CVE-2014-6271) , CVE-2014-7169

This new vulnerable in bash is spreading quickly over the Internet just like the heartbleed. How to know if your bash version is vulnerable?
For Linux
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
For Solaris 10
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
For Solaris 11
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

Solution is of course to patch or update to the latest version of bash. Go check out your OS for any updates now.

Tuesday, May 20, 2014

Starting spamd: child process [22173] exited or timed out without signaling production of a PID file

I upgraded spamassassin and encountered an error when trying to start it.
[root@nelsoncli Mail-SpamAssassin-3.4.0]# /etc/init.d/spamassassin start
Starting spamd: child process [22173] exited or timed out without signaling production of a PID file: exit 255 at /usr/bin/spamd line 2960.
                                                           [FAILED]
Solution: Run sa-update.

Monday, March 10, 2014

httpd: apr_sockaddr_info_get() failed for

Error:

[root@kraken htdocs]# /usr/local/apache2/bin/apachectl start
httpd: apr_sockaddr_info_get() failed for kraken
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[root@kraken htdocs]#

Solution:

Edit your httpd.conf and check the line

ServerName

You may put ServerName <hostname> or Server localhost