I have used this on my server <a href="http://bastille-linux.sourceforge.net/">http://bastille-linux.sourceforge.net/</a> ...<br><br><div class="gmail_quote">On Mon, Jun 2, 2008 at 9:44 AM, Ned Slider &lt;<a href="mailto:ned@unixmail.co.uk">ned@unixmail.co.uk</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Rogelio wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
John R Pierce wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
CentOS /is/ a distro, &nbsp;there is only one centos &#39;distribution&#39;. &nbsp; &nbsp; &nbsp;centos configured with selinux enabled, appropriate firewall rules, and the minimum number of services required for your application should be fairly &#39;hardened&#39; as-is.<br>

</blockquote>
<br>
Understood. &nbsp;I meant CentOS-based, but I suppose the &quot;best&quot; way is to just roll something myself.<br>
<br>
I was hoping to find a nice list HOWTO or script that someone else was using so I wouldn&#39;t have to think through everything from scratch.<br>
<br>
Thanks.<br>
</blockquote>
<br>
<br>
There are some guides around, for example:<br>
<br>
<a href="http://www.puschitz.com/SecuringLinux.shtml" target="_blank">http://www.puschitz.com/SecuringLinux.shtml</a><br>
<br>
However security is not a one size fits all solution that can be applied off the shelf. You need to assess where *your* risks are and what you should do to minimize them.<br>
<br>
Hope that helps.<br>
<br>
_______________________________________________<br>
CentOS mailing list<br>
<a href="mailto:CentOS@centos.org" target="_blank">CentOS@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos" target="_blank">http://lists.centos.org/mailman/listinfo/centos</a><br>
</blockquote></div><br>