@googlegroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of MdMonk
Sent: Friday, August 31, 2007 2:04 PM
To: ossec-list@googlegroups.com
Subject: [ossec-list] Re: OSSEC Web Interface--Unable to access ossec
directory
Props to Syndrowm for guiding me in figuring this out. Thanks Evan!
#
This will change
: [ossec-list] Re: OSSEC Web Interface--Unable to access ossec
directory
avc deny = SELinux problem. I'm not any SELinux guru, but you might be
able to fix this.
http://fedoraproject.org/wiki/SELinux/apache Gives a few pointers.
I *think* something like this will work until a proper SELinux policy
, 2007 5:33 PM
To: ossec-list
Subject: [ossec-list] Re: OSSEC Web Interface--Unable to access ossec
directory
avc deny = SELinux problem. I'm not any SELinux guru, but you might be
able to fix this.
http://fedoraproject.org/wiki/SELinux/apache Gives a few pointers.
I *think* something like
Found out the problem. On fedore 6 ,by default SE-Linux policy is
turned on.Once i turned off the SE_linux policy ,i was able to see the
web page content and logs.
On Aug 13, 4:16 pm, Robert5156 [EMAIL PROTECTED] wrote:
I followed the instructi0ons in the link below
avc deny = SELinux problem. I'm not any SELinux guru, but you might be
able to fix this.
http://fedoraproject.org/wiki/SELinux/apache Gives a few pointers.
I *think* something like this will work until a proper SELinux policy
is written for ossec:
chcon -R -h -t httpd_unconfined_script_exec_t
That's an selinux message. Are you running selinux in ENFORCING
mode? If so, you will have to grant the web server proc read-access to
the ossec directory/log files.
What do you have in your /etc/sysconfig/selinux config file?
-Chuck (mdmonk)
On 8/13/07, Robert5156 [EMAIL PROTECTED] wrote:
I
