public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH V5 0/5] audit by executable name
Date: Wed, 29 Oct 2014 16:05:38 -0400	[thread overview]
Message-ID: <10404139.lj6aruQcWX@x2> (raw)
In-Reply-To: <20141029194840.GL20866@madcap2.tricolour.ca>

On Wednesday, October 29, 2014 03:48:40 PM Richard Guy Briggs wrote:
> On 14/10/21, Paul Moore wrote:
> > > > Can anyone think of anything else that might be affected by this?
> > > 
> > > No one uses this stuff, just change it.
> > 
> > Yes, but I feel like I need to at least ask the question; how much
> > attention I pay to the answers is something else ...
> 
> I'm still skeptical this won't blow up...  Like the capabilities bitmap
> did.  I suspect there isn't agreement on what constitutes a feature.

Anything major that user space would have to know about to determine if its 
supported. If you don't know, just ask if we need to add a bit to the bitmap. 
Some examples, adding the object comparison engine, adding the loginuid-
immutable feature, if we added filtering on TTY that would also qualify (not 
asking for that). Otherwise, user space get EINVAL on the netlink operation 
which is not useful in explaining why the command was rejected.


> We just added a set/get features bitmap a year ago for things to be turned
> on/off and locked...  How does this features bitmap fit in with that
> features config?

I think of that as commanding the features, not determining if they exist.

> I don't disagree that a bitmap would be more useful for various
> distributions to pick and choose that which they choose to support over
> a version number that won't tell the whole story.

I also can be used to allow deprecation in a controlled way such that helpful 
messages are given to the system admin.

-Steve

  reply	other threads:[~2014-10-29 20:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03  3:06 [PATCH V5 0/5] audit by executable name Richard Guy Briggs
2014-10-03  3:06 ` [PATCH V5 1/5] audit: implement audit by executable Richard Guy Briggs
2014-10-03  3:06 ` [PATCH V5 2/5] audit: clean simple fsnotify implementation Richard Guy Briggs
2014-10-03  3:06 ` [PATCH V5 3/5] audit: convert audit_exe to audit_fsnotify Richard Guy Briggs
2014-10-03  3:06 ` [PATCH V5 4/5] audit: avoid double copying the audit_exe path string Richard Guy Briggs
2014-10-03  3:06 ` [PATCH V5 5/5] Revert "fixup! audit: clean simple fsnotify implementation" Richard Guy Briggs
2014-10-20 20:25 ` [PATCH V5 0/5] audit by executable name Steve Grubb
2014-10-20 22:47   ` Eric Paris
2014-10-20 23:02     ` Paul Moore
2014-10-20 23:33       ` Steve Grubb
2014-10-20 23:49         ` Steve Grubb
2014-10-21 21:56         ` Paul Moore
2014-10-21 22:06           ` Steve Grubb
2014-10-21 22:19           ` Eric Paris
2014-10-21 22:35             ` Paul Moore
2014-10-29 19:48               ` Richard Guy Briggs
2014-10-29 20:05                 ` Steve Grubb [this message]
2014-10-29 21:54                   ` Richard Guy Briggs
2014-10-29 23:59                     ` Eric Paris
2014-10-30  1:17                       ` Richard Guy Briggs
  -- strict thread matches above, loose matches on Subject: below --
2015-05-29 16:14 Peter Moody
2015-05-29 16:26 ` Paul Moore
2015-05-29 16:28 ` Richard Guy Briggs
2015-05-29 17:15   ` Peter Moody

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=10404139.lj6aruQcWX@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