From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] filterexcl: allow filterkey
Date: Tue, 13 Jun 2017 15:39:59 -0400 [thread overview]
Message-ID: <2910781.g0dc8Opiyj@x2> (raw)
In-Reply-To: <20170613184619.GH6203@madcap2.tricolour.ca>
On Tuesday, June 13, 2017 2:46:19 PM EDT Richard Guy Briggs wrote:
> > On 2017-06-12 20:05, Steve Grubb wrote:
> > > On Tuesday, April 4, 2017 6:39:22 AM EDT Richard Guy Briggs wrote:
> > > > The exclude rules did not permit a filterkey to be added. This isn't
> > > > as
> > > > important for the exclude filter compared to the others since no
> > > > records are generated with that key, but still helps identify rules
> > > > in the rules list configuration.
> > >
> > > How long ago did thkernel start allowing this? I'm trying to decide if
> > > this is generally applicable or needs some kind of versioning.
> >
> > I wasn't aware it was disallowed previously. I'll try to dig out if
> > that was previously refused.
>
> I see nothing obvious going back to its introduction:
> 5adc8a6adc91 <amy.griffis@hp.com> 2006-06-14 ("add rule filterkey")
I think I remember that it was never supported because it didn't make sense to
have a key that would never be used for anything. Exclude supresses records
just like a 'never' action. The key is rejected to catch someone's attention
that they might have made a copy and paste to the wrong filter.
-Steve
next prev parent reply other threads:[~2017-06-13 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 10:39 [PATCH] filterexcl: allow filterkey Richard Guy Briggs
2017-06-13 0:05 ` Steve Grubb
2017-06-13 2:47 ` Richard Guy Briggs
2017-06-13 18:46 ` Richard Guy Briggs
2017-06-13 19:39 ` Steve Grubb [this message]
2017-06-13 19:58 ` Richard Guy Briggs
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=2910781.g0dc8Opiyj@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=rgb@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