From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Dennis Subject: Re: [PATCH] Fix acct quoting in audit_log_acct_message()) Date: Tue, 04 Mar 2008 15:29:10 -0500 Message-ID: <47CDB116.7010007@redhat.com> References: <47CCC6F0.1090005@redhat.com> <47CD65A3.8020204@redhat.com> <1204654248.12783.32.camel@vespa.frost.loc> <200803041356.19571.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200803041356.19571.sgrubb@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Steve Grubb Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com Steve Grubb wrote: > If there's no agreement with them, should we change anything? > auparse is working pretty good as is. No it's not. The auparse approach is based on tables, tables which have been shown to be incorrect and tied to kernel versions and the patch set used to build that kernel version. Like it or not, audit data is and will be divorced from kernel versions. In fact audit data will derive from a mix of different kernel versions if the audit data is aggregated, which is the plan. In the current scheme there is no realistic way to process audit data from thousands of nodes all running different kernels in an enterprise wide auditing system. Any scheme which requires knowing the kernel version and patch set to correctly read the data is broken. Attempts to cast this issue as pandering to userspace weenies is off the mark by a mile. -- John Dennis