From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Preferred subj= with multiple LSMs Date: Tue, 16 Jul 2019 12:37:38 -0400 Message-ID: <9150011.WShEb2oc6S@x2> References: <3577098.oGDFHdoSSQ@x2> <201113d1-192f-d6b3-17bb-bcf219bc5f15@magitekltd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201113d1-192f-d6b3-17bb-bcf219bc5f15@magitekltd.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: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Tuesday, July 16, 2019 12:33:30 PM EDT Lenny Bruzenak wrote: > On 7/16/19 11:14 AM, Steve Grubb wrote: > > Quoting has a specific meaning in audit fields. So, we really shouldn't > > do > > that. We can simply pick another field delimiter. I really don't care > > which it is as long as its illegal for use in a label. For example, we > > use > > > > #define AUDIT_KEY_SEPARATOR 0x01 > > > > to separate key fields. We can pick almost anything. (exclamation mark, > > semi- colon, hash, plus symbol, tilde, 0x02, whatever) But it will need > > to be documented and put into the API so that everyone is aware of the > > convention. > > > > -Steve > > Also should it not be the "#define AUDIT_INTERP_SEPARATOR 0x1D" for > enriched format records? True. That one is disqualified, too. -Steve