public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: audisp plugin policy question(s)
Date: Wed, 22 Oct 2008 12:53:53 -0400	[thread overview]
Message-ID: <200810221253.54018.sgrubb@redhat.com> (raw)
In-Reply-To: <1224693984.14755.115.camel@homeserver>

On Wednesday 22 October 2008 12:46:24 LC Bruzenak wrote:
> In the audisp plugin sources (and audit.spec), the zos-remote plugin has
> a policy section, the others do not. Will those pieces be added
> similarly? Should prelude/prelude-plugin/remote-plugin policy go here or
> in the system policy rpm?

No. I removed SE Linux policy in this commit last week:

https://fedorahosted.org/audit/changeset/134


> Right now my prelude-manager runs ranged SystemLow-SystemHigh.
> Should this be only SystemHigh?

I would put the prelude manager and correlator at the same level as the audit 
daemon since they get parts of the audit logs in events. So, if auditd is 
ranged, prelude should be.


> There are some spool files not set accordingly which cause AVCs.
> I guess these need file contexts?

Yep. Those spools are likely storage for transmissions while prelude-manager 
is down.


> Then there is a prelude-manager<->prelude-lml question, but I won't get
> into that in case I hear "take it up with the prelude guys" from the
> above.

I would take it up with them iff you have a reproducable problem when not in 
MLS. If its only shows up when on MLS, you likely have a policy problem.

-Steve

  reply	other threads:[~2008-10-22 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 16:46 audisp plugin policy question(s) LC Bruzenak
2008-10-22 16:53 ` Steve Grubb [this message]
2008-10-22 18:15   ` LC Bruzenak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200810221253.54018.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox