public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Linda Knippers <linda.knippers@hp.com>
Cc: linux-audit@redhat.com
Subject: Re: [RFC] Do away with entry filter
Date: Fri, 27 Feb 2009 12:40:11 -0500	[thread overview]
Message-ID: <200902271240.12137.sgrubb@redhat.com> (raw)
In-Reply-To: <49A81B59.1050608@hp.com>

On Friday 27 February 2009 11:56:57 am Linda Knippers wrote:
> > Let's discuss...
>
> Without "entry", does "exit" still make sense?

You mean the name? I think so for a compatibility perspective. Not everyone 
will change their rules right away. Are you suggesting to rename the exit 
filter to something more generic?


> In other words, are the choices really just "always" and "never"?

For syscall, yes. There are still task, exclude, and user filters. Of these, I 
can't think of any use for the task filter anymore either. I think at one 
time it, too, was envisioned to help select the right tasks for auditing. 


> If we're going to change things, is this an opportunity to simplify in
> general? 

I wouldn't mind losing task filter, too. But I was thinking mostly of the case 
where entry rules identify a syscal is auditable and then the exit filter is 
99% of the time walked in its entirety before deciding nothing to do.

-Steve

  reply	other threads:[~2009-02-27 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 14:54 [RFC] Do away with entry filter Steve Grubb
2009-02-27 16:56 ` Linda Knippers
2009-02-27 17:40   ` Steve Grubb [this message]
2009-02-27 17:48     ` Linda Knippers
2009-02-27 18:19       ` Steve Grubb
2009-02-27 19:27         ` Linda Knippers
2009-02-27 20:14         ` Eric Paris
2009-02-27 21:18           ` Steve Grubb
2009-07-28 18:26 ` Steve Grubb

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=200902271240.12137.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linda.knippers@hp.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