Am Montag, den 21.02.2011, 14:37 +0100 schrieb Christoph Maser:
Am Sonntag, den 20.02.2011, 22:47 +0100 schrieb Pavel Kankovsky:
On Thu, 17 Feb 2011, Christoph Maser wrote:
Where is that from?
Examine the binary policy with apol or sesearch.
I took the c5 SRMP and ran rpmbuild
On Thu, 17 Feb 2011, Christoph Maser wrote:
Where is that from?
Examine the binary policy with apol or sesearch.
I took the c5 SRMP and ran rpmbuild -bp, in my BUILD
dir i dont see those:
/home/cmr/rpmbuild/BUILD/serefpolicy-2.4.6/policy/modules/services: grep
initrc nagios*
- nothing
On Mon, 21 Feb 2011, Christoph Maser wrote:
Thanks for the pointers, I still couldn't find out why its not working.
Actually it doesn't produce any denials in audit.log.
Have you tried semodule -i enableaudit.pp?
--
Pavel Kankovsky aka Peak / Jeremiah 9:21\
Am Mittwoch, den 16.02.2011, 23:34 +0100 schrieb Christoph Maser:
I have to correct myself, actually /var/spool/nagios is in the policy. I
did only look at the source files of selinux-policy but there is also a
huge patch in that package wich includes a lot of nagios policy changes.
But I
Scott Reese wrote:
Greetings:
I've been looking at the SELinux policy as it relates to Nagios. It's
been a learning experience, and I now fully understand why people just
turn SELinux off. What a hassle. In any event, I've isolated the
issues, and I'm looking for advice from those of you
Hi,
EPEL6 (beta) ships nagios-3.2.3, I would assume that the SELinux nagios
policy was set up for that build.
Regards,
On Wed, 2011-01-05 at 10:01 -0500, Scott Reese wrote:
Greetings:
I've been looking at the SELinux policy as it relates to Nagios. It's
been a learning experience, and I
Am Mittwoch, den 05.01.2011, 16:19 +0100 schrieb Yury V. Zaytsev:
On Wed, 2011-01-05 at 15:14 +, Eirikur Hjartarson wrote:
Hi,
EPEL6 (beta) ships nagios-3.2.3, I would assume that the SELinux nagios
policy was set up for that build.
Maybe we should adjust our package to match
On Wed, 22 Dec 2010, Scott Reese wrote:
My apologies. Since I wasn't seeing anything in the audit log I assumed
that SELinux wasn't the problem. However, I disabled it and the problem
went away.
It might have hit a dontaudit rule. Some access failures are expected
or even intended and
Just to be sure. Can to disable SELinux and try it again? So we can exclude
this?
My apologies. Since I wasn't seeing anything in the audit log I assumed
that SELinux wasn't the problem. However, I disabled it and the problem
went away.
I will troubleshoot this as an SELinux issue.
On Wed, 2010-12-22 at 08:43 -0500, Scott Reese wrote:
I will troubleshoot this as an SELinux issue.
Thanks for your help.
Hi!
Please keep us posted if you come up with a SELinux module to solve this
issue. I wonder if it can be packaged along with Nagios...
--
Sincerely yours,
Yury V.
10 matches
Mail list logo