<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Linux Admin Zone &#187; Security</title>
	<atom:link href="http://linuxadminzone.com/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://linuxadminzone.com</link>
	<description>Adding more reasons to celebrate Open Source.</description>
	<lastBuildDate>Thu, 29 Jul 2010 17:25:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Here is why GoDaddy sucks in hosting, what about alternative?</title>
		<link>http://linuxadminzone.com/here-is-why-godaddy-sucks-in-hosting-what-about-alternative/</link>
		<comments>http://linuxadminzone.com/here-is-why-godaddy-sucks-in-hosting-what-about-alternative/#comments</comments>
		<pubDate>Thu, 29 Jul 2010 17:24:57 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[godaddy]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[malware]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=218</guid>
		<description><![CDATA[Hosting my wordpress blog in GoDaddy was a big mistake, I realized this when one of my regular visitor alerted me that my blog is having suspicious activity. I promptly downloaded all of my blog files in my local system to scan and that operation took around 2 hours because of terrible FTP download rate [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/here-is-why-godaddy-sucks-in-hosting-what-about-alternative/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Disable ssl ver 2 in apache for pci compliance</title>
		<link>http://linuxadminzone.com/disable-ssl-ver-2-in-apache-for-pci-compliance/</link>
		<comments>http://linuxadminzone.com/disable-ssl-ver-2-in-apache-for-pci-compliance/#comments</comments>
		<pubDate>Sat, 23 Jan 2010 16:36:51 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Server]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[ssl]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=157</guid>
		<description><![CDATA[You need to disable SSL ver 2 and enable SSL ver 3 in apache for PCI compliance. Its very easy to do. Following settings will set SSL ver 3 and also disable older/unsecure cipher suite in Redhat/centos/fedora Linux server: 1. Open /etc/httpd/conf.d/ssl.conf and add or if these lines already there, edit them as per follows: [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/disable-ssl-ver-2-in-apache-for-pci-compliance/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Quickly change your ssh port from default 22 to something higher</title>
		<link>http://linuxadminzone.com/quickly-change-your-ssh-port-from-default-22-to-something-higher/</link>
		<comments>http://linuxadminzone.com/quickly-change-your-ssh-port-from-default-22-to-something-higher/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 12:12:46 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[ssh port security]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=36</guid>
		<description><![CDATA[In the era of daily brute force attacks, it is advisable to change your ssh port from defaul 22 to something higher to lower your chances of being a victim. I&#8217;m using CentOS 5.2 box here but the process should be identical in other RH based distros. 1. Update /etc/ssh/sshd_config file, line 13 (it might [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/quickly-change-your-ssh-port-from-default-22-to-something-higher/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Install and configure ntop for network stats, monitoring</title>
		<link>http://linuxadminzone.com/install-and-configure-ntop-for-network-stats-monitoring/</link>
		<comments>http://linuxadminzone.com/install-and-configure-ntop-for-network-stats-monitoring/#comments</comments>
		<pubDate>Sat, 29 Nov 2008 07:10:33 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[ntop]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=30</guid>
		<description><![CDATA[ntop is one of the most powerful and easy to use tool for network traffic statistics viewing and analysis. Here are quick steps to install it on CentOS 5.2 box (upgraded from 5.0 release). Try to install in easy way: # yum install ntop Most probably yum get failed for missing dependencies such as rrdtool [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/install-and-configure-ntop-for-network-stats-monitoring/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Block IP Address in FreeBSD</title>
		<link>http://linuxadminzone.com/block-ip-address-in-freebsd/</link>
		<comments>http://linuxadminzone.com/block-ip-address-in-freebsd/#comments</comments>
		<pubDate>Tue, 11 Nov 2008 07:07:29 +0000</pubDate>
		<dc:creator>jagbir</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[freebsd security]]></category>

		<guid isPermaLink="false">http://linuxadminzone.com/?p=29</guid>
		<description><![CDATA[The simple method is to add the offensive IP in your /etc/hosts.allow file and deny any access to that: # ee /etc/hosts.allow (and add following line in it) all: :deny You can also use one quick and dirty hack: # route add 127.0.0.1 All ACKs to specified IP address would be headed to 127.0.0.1, means [...]]]></description>
		<wfw:commentRss>http://linuxadminzone.com/block-ip-address-in-freebsd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
