From mboxrd@z Thu Jan 1 00:00:00 1970 From: LC Bruzenak Subject: Re: get_field_str() and interpret_field() bug with multi-word fields Date: Tue, 12 Aug 2008 14:02:35 -0500 Message-ID: <1218567755.7022.89.camel@homeserver> References: <0E43BF2D7491F0468B56B1A5C493866B020DD0F1@SAT4MX07.RACKSPACE.CORP> <1218564336.7022.72.camel@homeserver> <48A1DBEB.1080501@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <48A1DBEB.1080501@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: John Dennis Cc: William Kelly , Bret Piatt , Linux-audit@redhat.com List-Id: linux-audit@redhat.com On Tue, 2008-08-12 at 14:52 -0400, John Dennis wrote: ... > > FWIW, I think the proper encoding should be that all string values are > enclosed in double quotes and the string encoding follows the same > backslash escaping defined for the C language which was subsequently > adopted by many other system components which would make it instantly > familiar and parseable by many tools. This would be a very simple and > welcome fix. IIRC there were objections to the double-quotes but that would work for me too. LCB. -- LC (Lenny) Bruzenak lenny@magitekltd.com