From: Steve Grubb <sgrubb@redhat.com>
To: Paul Moore <pmoore@redhat.com>
Cc: Richard Guy Briggs <rgb@redhat.com>, linux-audit@redhat.com
Subject: Re: [userspace PATCH v2 0/2] Add support for loginuid_set
Date: Tue, 11 Oct 2016 12:40:55 -0400 [thread overview]
Message-ID: <2160607.4V3FbIfBlX@x2> (raw)
In-Reply-To: <CAGH-KgvR7BmJXYAhh1ovDK10adMXnbRm9=bzh2Efcgt4Wcq4LQ@mail.gmail.com>
On Monday, October 10, 2016 5:10:39 PM EDT Paul Moore wrote:
> On Mon, Oct 10, 2016 at 1:24 PM, Steve Grubb <sgrubb@redhat.com> wrote:
> > On Thursday, August 18, 2016 2:18:55 PM EDT Richard Guy Briggs wrote:
> >> loginuid_set support should have been added to userspace when it was
> >> added to the kernel around v3.10. Add it before we do similar for
> >> sessionID and sessionID_set.
> >
> > If this were accepted, how would this change writing rules? IOW, can you
> > give an example rule so we can see what this looks like?
>
> We have a RFE feature page which documents some rule examples:
>
> *
> https://github.com/linux-audit/audit-kernel/wiki/RFE-Session-ID-User-Filter
OK, thanks. This is helpful. So, what is the difference between these rules?
-a always,exit -F path=/tmp/sessionid_test -F loginuid=-1
-a always,exit -F path=/tmp/sessionid_set_test -F loginuid_set=0
-Steve
next prev parent reply other threads:[~2016-10-11 16:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 18:18 [userspace PATCH v2 0/2] Add support for loginuid_set Richard Guy Briggs
2016-08-18 18:18 ` [userspace PATCH v2 1/2] get feature list only once Richard Guy Briggs
2016-08-18 18:18 ` [userspace PATCH v2 2/2] Add user filter option loginuid_set from uapi macro AUDIT_LOGINUID_SET Richard Guy Briggs
2016-10-10 17:24 ` [userspace PATCH v2 0/2] Add support for loginuid_set Steve Grubb
2016-10-10 21:10 ` Paul Moore
2016-10-11 16:40 ` Steve Grubb [this message]
2016-10-11 18:27 ` Richard Guy Briggs
2016-10-11 19:22 ` Steve Grubb
2016-10-11 20:42 ` Paul Moore
2016-10-11 20:50 ` Steve Grubb
2016-10-11 20:54 ` Paul Moore
2016-10-11 21:31 ` Steve Grubb
2016-10-11 22:15 ` Paul Moore
2016-10-17 15:40 ` Richard Guy Briggs
2016-10-17 16:04 ` Steve Grubb
2016-10-17 16:51 ` Richard Guy Briggs
2016-10-17 17:06 ` Steve Grubb
2016-10-17 21:19 ` Paul Moore
2016-10-17 22:21 ` Steve Grubb
2016-10-18 4:35 ` Richard Guy Briggs
2016-10-18 10:48 ` 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=2160607.4V3FbIfBlX@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=pmoore@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