<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
David Hoffman wrote:
<blockquote cite="mid94c79020504071110fd60a74@mail.gmail.com"
type="cite">
<pre wrap="">On Apr 7, 2005 1:04 PM, Alexander Dalloz <a class="moz-txt-link-rfc2396E" href="mailto:ad+lists@uni-x.org"><ad+lists@uni-x.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Am Do, den 07.04.2005 schrieb jeffrey Lang um 19:59:
</pre>
<blockquote type="cite">
<pre wrap="">Verify that you have turned off SElinux, check the file
/etc/selinux/config, make sure that SELINUX=disabled and not enforcing
or something else. I had this same type of problem with apache and perl.
jeff
</pre>
</blockquote>
<pre wrap="">No good advise! Why do you say so? Don't switch off security settings
just because you don't know how to deal with them correctly. There is
documentation
<a class="moz-txt-link-freetext" href="http://fedora.redhat.com/docs/selinux-apache-fc3/">http://fedora.redhat.com/docs/selinux-apache-fc3/</a>
</pre>
</blockquote>
<pre wrap=""><!---->
I'll second that statement. Sure, there are times when you might have
a server in a well protected environment, and don't have any need for
SELinux, and it may be safe to suggest turning it off. But for the
majority of users and environments, you will want to keep it on.
Find out why the door is closed, and learn how to open it.
Don't knock a big hole through it so anyone can come in.
</pre>
</blockquote>
I guess i should have added that you should verify this, and then
slowly add back in the security, so you know what works and what
doesn't. I agree that this would cause a security hole, if left
disabled.<br>
</body>
</html>