<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: 10 Things You Should Secure on Your Linux Server</title>
	<atom:link href="http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/</link>
	<description>Home of the 10,000% Guarantee</description>
	<lastBuildDate>Fri, 22 May 2009 00:24:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3330</generator>
	<item>
		<title>By: Bryan Levine</title>
		<link>http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/comment-page-1/#comment-12566</link>
		<dc:creator>Bryan Levine</dc:creator>
		<pubDate>Thu, 03 Apr 2008 15:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/#comment-12566</guid>
		<description>@ Ron, 
These steps can be applied to either a web server or a file server depending on if the server is public or private. If you have a private server, such as a back-end database that has no public IP addresses, these settings may not assist you in securing the private server. In that case, ensuring security on your  public servers becomes even more important.</description>
		<content:encoded><![CDATA[<p>@ Ron,<br />
These steps can be applied to either a web server or a file server depending on if the server is public or private. If you have a private server, such as a back-end database that has no public IP addresses, these settings may not assist you in securing the private server. In that case, ensuring security on your  public servers becomes even more important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ron</title>
		<link>http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/comment-page-1/#comment-12564</link>
		<dc:creator>ron</dc:creator>
		<pubDate>Thu, 03 Apr 2008 00:51:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/#comment-12564</guid>
		<description>Are these steps for a file sever or web server.</description>
		<content:encoded><![CDATA[<p>Are these steps for a file sever or web server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Sheehan</title>
		<link>http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/comment-page-1/#comment-12519</link>
		<dc:creator>Michael Sheehan</dc:creator>
		<pubDate>Fri, 15 Feb 2008 16:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/#comment-12519</guid>
		<description>@ Dave,
Thank you for your very details corrections and clarifications. I have edited the post and converted the commands to &quot;preformatted&quot; format so that WordPress (hopefully) will not display the wrong characters. I have also tried to replace the curly quotes, where possible.

Please don&#039;t hesitate to provide further corrections/clarifications. Again, I appreciate the time you have taken to audit this post.

-Michael</description>
		<content:encoded><![CDATA[<p>@ Dave,<br />
Thank you for your very details corrections and clarifications. I have edited the post and converted the commands to &#8220;preformatted&#8221; format so that WordPress (hopefully) will not display the wrong characters. I have also tried to replace the curly quotes, where possible.</p>
<p>Please don&#8217;t hesitate to provide further corrections/clarifications. Again, I appreciate the time you have taken to audit this post.</p>
<p>-Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/comment-page-1/#comment-12518</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 15 Feb 2008 12:11:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/#comment-12518</guid>
		<description>@ tallman:

1. # ls -l /etc/rc2.d/S* &#124; cut –d/ -f6

Wordpress messes up dashes.  I found that the &quot;-l&quot; in the above command told ls to go and look for a file named -l rather than list the files in the long format.  Just delete the dash and re-type it to make the command work.  You may be able to see the differences in the size of the dash depending on what font your terminal is using.

2. find / -path /proc –prune –o –perm -2 ! –type 1 –ls

Wordpress has messed up the dashes here as well but once you have fixed that you will find that &quot;-type 1&quot; doesn&#039;t work.  The correct command should be &quot;-type l&quot; which is a lower case &quot;L&quot;.  This will ignore symbolic links because their ownership is not really that important.

3. ls –l /etc/rc2.d/S* &#124; cut –d/ -f6

This command worked fine for me on Ubuntu once the dashes were fixed.

4. egrep –v ‘.*:\*&#124;:!’ /etc/shadow&#124;awk -F: ‘{print $1}’

Wordpress messes up apostrophes as well and turns them into some sort of &quot;smart quote&quot;.  You will need to replace the single quotes in the above command just as you did with the dashes.  You will still need to replace the dashes as well.  This command worked fine for me with the spaces either side of the pipe but this will be dependent on your shell.

All of these commands apart from 3. will need to be run as root or with sudo in front of them.  Only root can read the shadow file and the find commands will not have permission to look in certain directories unless you run it as root.

Adding the -n option to the &quot;netstat -tulp&quot; command may make it complete much faster as it won&#039;t have to do reverse DNS lookups on every IP address.  This can make quite a difference on busy systems.

I&#039;m not going to make any comment on the quality of the security improvements these 10 command will make other than to say that security is hard.  Following these commands may make you &quot;more&quot; secure but they won&#039;t make you &quot;absolutely&quot; secure.  Don&#039;t start believing that you are invulnerable now that you have a firewall.</description>
		<content:encoded><![CDATA[<p>@ tallman:</p>
<p>1. # ls -l /etc/rc2.d/S* | cut –d/ -f6</p>
<p>Wordpress messes up dashes.  I found that the &#8220;-l&#8221; in the above command told ls to go and look for a file named -l rather than list the files in the long format.  Just delete the dash and re-type it to make the command work.  You may be able to see the differences in the size of the dash depending on what font your terminal is using.</p>
<p>2. find / -path /proc –prune –o –perm -2 ! –type 1 –ls</p>
<p>Wordpress has messed up the dashes here as well but once you have fixed that you will find that &#8220;-type 1&#8243; doesn&#8217;t work.  The correct command should be &#8220;-type l&#8221; which is a lower case &#8220;L&#8221;.  This will ignore symbolic links because their ownership is not really that important.</p>
<p>3. ls –l /etc/rc2.d/S* | cut –d/ -f6</p>
<p>This command worked fine for me on Ubuntu once the dashes were fixed.</p>
<p>4. egrep –v ‘.*:\*|:!’ /etc/shadow|awk -F: ‘{print $1}’</p>
<p>Wordpress messes up apostrophes as well and turns them into some sort of &#8220;smart quote&#8221;.  You will need to replace the single quotes in the above command just as you did with the dashes.  You will still need to replace the dashes as well.  This command worked fine for me with the spaces either side of the pipe but this will be dependent on your shell.</p>
<p>All of these commands apart from 3. will need to be run as root or with sudo in front of them.  Only root can read the shadow file and the find commands will not have permission to look in certain directories unless you run it as root.</p>
<p>Adding the -n option to the &#8220;netstat -tulp&#8221; command may make it complete much faster as it won&#8217;t have to do reverse DNS lookups on every IP address.  This can make quite a difference on busy systems.</p>
<p>I&#8217;m not going to make any comment on the quality of the security improvements these 10 command will make other than to say that security is hard.  Following these commands may make you &#8220;more&#8221; secure but they won&#8217;t make you &#8220;absolutely&#8221; secure.  Don&#8217;t start believing that you are invulnerable now that you have a firewall.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Levine</title>
		<link>http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/comment-page-1/#comment-12517</link>
		<dc:creator>Bryan Levine</dc:creator>
		<pubDate>Thu, 14 Feb 2008 17:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/#comment-12517</guid>
		<description>Tallman, 

From the commands you&#039;ve posted, there is an error in your syntax. Any commands containing a pipe (&#124;) require a space on either side of the pipe. It should be:

# egrep –v ‘.*:\* &#124; :!’ /etc/shadow &#124; awk -F: ‘{print $1}’

Thanks.</description>
		<content:encoded><![CDATA[<p>Tallman, </p>
<p>From the commands you&#8217;ve posted, there is an error in your syntax. Any commands containing a pipe (|) require a space on either side of the pipe. It should be:</p>
<p># egrep –v ‘.*:\* | :!’ /etc/shadow | awk -F: ‘{print $1}’</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tallman</title>
		<link>http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/comment-page-1/#comment-12516</link>
		<dc:creator>tallman</dc:creator>
		<pubDate>Thu, 14 Feb 2008 13:14:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.servepath.com/2008/02/13/10-things-you-should-secure-on-your-linux-server/#comment-12516</guid>
		<description>Most of the commands don&#039;t work at all, did you test them before posting them?
# find / -path /proc –prune –o –perm -2 ! –type 1 –ls
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
# find / -path /proc –prune –o –nouser –o –nogroup
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
#  ls –l /etc/rc2.d/S* &#124; cut –d/ -f6
cut: –d/: No such file or directory
ls: –l: No such file or directory
ls: /etc/rc2.d/S*: No such file or directory
#  egrep –v &#039;.*:\*&#124;:!&#039; /etc/shadow&#124;awk -F: &#039;{print $1}&#039;
grep: .*:\*&#124;:!: No such file or directory

PS
tested on Debian etch, same results on ubuntu 7.10</description>
		<content:encoded><![CDATA[<p>Most of the commands don&#8217;t work at all, did you test them before posting them?<br />
# find / -path /proc –prune –o –perm -2 ! –type 1 –ls<br />
find: paths must precede expression<br />
Usage: find [-H] [-L] [-P] [path...] [expression]<br />
# find / -path /proc –prune –o –nouser –o –nogroup<br />
find: paths must precede expression<br />
Usage: find [-H] [-L] [-P] [path...] [expression]<br />
#  ls –l /etc/rc2.d/S* | cut –d/ -f6<br />
cut: –d/: No such file or directory<br />
ls: –l: No such file or directory<br />
ls: /etc/rc2.d/S*: No such file or directory<br />
#  egrep –v &#8216;.*:\*|:!&#8217; /etc/shadow|awk -F: &#8216;{print $1}&#8217;<br />
grep: .*:\*|:!: No such file or directory</p>
<p>PS<br />
tested on Debian etch, same results on ubuntu 7.10</p>
]]></content:encoded>
	</item>
</channel>
</rss>
