From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [userspace PATCH v2 0/2] Add support for loginuid_set Date: Mon, 17 Oct 2016 13:06:02 -0400 Message-ID: <1620326.R8YxsBdKvy@x2> References: <1471544337-3108-1-git-send-email-rgb@redhat.com> <1658401.VrPGUNHXAh@x2> <20161017165153.GG23701@madcap2.tricolour.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20161017165153.GG23701@madcap2.tricolour.ca> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Richard Guy Briggs Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Monday, October 17, 2016 12:51:53 PM EDT Richard Guy Briggs wrote: > On 2016-10-17 12:04, Steve Grubb wrote: > > 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? > > Sure, then we would have two ways to express the same thing and ends up > using in-band signalling which is what Eric was trying to avoid in the > first place. The plan would be to not use sessionid_set at all. Then we have one way to do things. I doubt anyone is using either of the set functions. Just mark them deprecated in the comments. -Steve