From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Paris Subject: Re: [PATCH] auparse: apparmor fields Date: Mon, 20 Feb 2012 10:09:46 -0500 Message-ID: <1329750586.2337.39.camel@localhost> References: <1329482562-21751-1-git-send-email-mhcerri@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1329482562-21751-1-git-send-email-mhcerri@linux.vnet.ibm.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: Marcelo Cerri Cc: linux-audit@redhat.com, gcwilson@us.ibm.com, bryntcor@us.ibm.com List-Id: linux-audit@redhat.com On Fri, 2012-02-17 at 10:42 -0200, Marcelo Cerri wrote: > I'd like to know if these fields should be treated the same way as escaped > fields by libauparse or maybe it should be changed in the kernel. Users of the audit system may choose to use it however they like. Steve and I have agreed to disagree (or at least realized that we will never agree) on the use of 'audit_log_string'. As the audit kernel maintainer I will not ask AppArmor to change what they use and I will continue to request more users of the kernel audit system to use the *log_string functions instead of using %s. Given that, I think the only reasonable option is your patch, so thank you so much!