Linux-audit Archive on lore.kernel.org
 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: [userspace PATCH v2 0/2] Add support for loginuid_set
Date: Mon, 17 Oct 2016 12:04:33 -0400	[thread overview]
Message-ID: <1658401.VrPGUNHXAh@x2> (raw)
In-Reply-To: <20161017154017.GF23701@madcap2.tricolour.ca>

On Monday, October 17, 2016 11:40:17 AM EDT Richard Guy Briggs wrote:
> Since sessionid is a new field for filter specification (but not
> reporting and searching), I blocked sessionid==-1 in the api for setting
> filters.  This unfortunately makes it a different way to specify it than
> loginuid when it is not set.

Can we unblock that?

-Steve

  reply	other threads:[~2016-10-17 16:04 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
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 [this message]
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=1658401.VrPGUNHXAh@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