From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Dennis Subject: Re: Cooked audit log format Date: Tue, 13 May 2008 08:30:05 -0400 Message-ID: <482989CD.5070804@redhat.com> References: <482767E0.10506@redhat.com> <200805121043.17906.sgrubb@redhat.com> <48285C0C.5070809@redhat.com> <200805121119.46856.sgrubb@redhat.com> <48286C72.3020106@redhat.com> <1210625783.3228.42.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1210625783.3228.42.camel@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Eric Paris Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com Eric Paris wrote: > On Mon, 2008-05-12 at 12:12 -0400, John Dennis wrote: >> It should also be a goal that correct parsing of audit logs not be >> dependent on specific kernel versions. > > I've heard you say this a number of times. Can you let me know specific > examples of what you had to code around due to specific kernel versions > since the audit system started to settle down? The set of strings which are encoded in hex vary depending on kernel version. That set of special audit fields currently must be hard coded into any code which attempts to parse audit output or the parsing will fail, sometimes catastrophically. A list of these special field values differing between two popular kernel versions has been previously posted to this list. That list is not complete. If the rules for string encoding were proper and regular this issue would not exist. -- John Dennis