From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Draft copy of how to write good events Date: Mon, 08 Sep 2014 14:35:39 -0400 Message-ID: <1602023.AXj9xOFLuL@x2> References: <3228354.4toYKCVf1H@x2> <20140904220423.GA26201@madcap2.tricolour.ca> <20140904220806.GB26201@madcap2.tricolour.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140904220806.GB26201@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 Thursday, September 04, 2014 06:08:06 PM Richard Guy Briggs wrote: > > I assume the mix of new-, new_, old- and old_ are there due to > > historical raisins and changing them would break userspace... Yes it would. It can break more than ausearch. For example, there could be an analysis script that does this: while au.parse_next_event(): if au.find_field("new_gid"): do_something() Changing the event would cause the program to not find the event it was looking for. > > Here's a unified diff of a few obvious minor cleanups... I took most of these changes and added some more changes of my own. A revised copy has been uploaded. -Steve