From: Linda Knippers <linda.knippers@hp.com>
To: Matthew Booth <mbooth@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: Not auditing dispatchers
Date: Fri, 06 Jun 2008 18:53:01 -0400 [thread overview]
Message-ID: <4849BFCD.2080808@hp.com> (raw)
In-Reply-To: <48492BBC.40400@redhat.com>
You could construct your audit rules dynamically so that they
exclude the dispatcher. You'd have to know its pid and then have
a -F pid!= xxx option on your audit rules. I haven't tried that
but it should work. You'd have to re-do the rules if the dispatcher
was restarted so its kind of clunky.
I think the feature that LAuS had for letting trusted programs
enable/disable auditing of themselves was kind of handy.
-- ljk
Matthew Booth wrote:
> The kernel ignores auditable events from the audit daemon, but is there
> an 'approved' way to achieve the same for dispatchers? The problem is
> the same, in that you get an infinite loop if the dispatcher itself
> performs any action which generates an audit record.
>
> Thanks,
>
> Matt
prev parent reply other threads:[~2008-06-06 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 12:21 Not auditing dispatchers Matthew Booth
2008-06-06 22:53 ` Linda Knippers [this message]
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=4849BFCD.2080808@hp.com \
--to=linda.knippers@hp.com \
--cc=linux-audit@redhat.com \
--cc=mbooth@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