From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miloslav Trmac Subject: Re: Thoughts on adding sd-journal as a log_format to auditd Date: Fri, 15 Mar 2013 11:22:50 -0400 (EDT) Message-ID: <1738104947.8168390.1363360970843.JavaMail.root@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx4-phx2.redhat.com (mx02.colomx.prod.int.phx2.redhat.com [10.5.7.2]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r2FFMon5017916 for ; Fri, 15 Mar 2013 11:22:50 -0400 In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: George McCollister Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com ----- Original Message ----- > 2) Write an audispd plugin that used the sd-journal API to store > audit events in the journal. > > 3) Add sd-journal as a log format to auditd. Both of these will run into the problem recently discussed on this mailing list: the available methods to parse an audit records into fields are a bit imprecise/"lossy" because not all records keep the name=value format as expected. This can be OK if auparse is able to extract all the data you need/expect to process. Mirek