From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Preferred subj= with multiple LSMs
Date: Tue, 16 Jul 2019 12:37:38 -0400 [thread overview]
Message-ID: <9150011.WShEb2oc6S@x2> (raw)
In-Reply-To: <201113d1-192f-d6b3-17bb-bcf219bc5f15@magitekltd.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
next prev parent reply other threads:[~2019-07-16 16:37 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 16:33 Preferred subj= with multiple LSMs Casey Schaufler
2019-07-12 16:33 ` Casey Schaufler
2019-07-13 15:08 ` Steve Grubb
2019-07-13 15:08 ` Steve Grubb
2019-07-15 19:04 ` Richard Guy Briggs
2019-07-15 19:04 ` Richard Guy Briggs
2019-07-15 19:37 ` Casey Schaufler
2019-07-15 21:28 ` Paul Moore
2019-07-15 22:55 ` Steve Grubb
2019-07-16 16:00 ` Casey Schaufler
2019-07-16 16:14 ` Steve Grubb
2019-07-16 16:33 ` Lenny Bruzenak
2019-07-16 16:37 ` Steve Grubb [this message]
2019-07-16 17:16 ` Casey Schaufler
2019-07-16 17:16 ` Casey Schaufler
2019-07-16 17:12 ` Paul Moore
2019-07-16 17:29 ` Casey Schaufler
2019-07-16 17:29 ` Casey Schaufler
2019-07-16 17:43 ` Paul Moore
2019-07-16 17:43 ` Paul Moore
2019-07-16 17:58 ` Casey Schaufler
2019-07-16 17:58 ` Casey Schaufler
2019-07-16 18:06 ` Steve Grubb
2019-07-16 18:06 ` Steve Grubb
2019-07-16 18:41 ` Casey Schaufler
2019-07-16 18:41 ` Casey Schaufler
2019-07-16 21:25 ` Paul Moore
2019-07-16 21:25 ` Paul Moore
2019-07-16 21:46 ` Steve Grubb
2019-07-16 21:46 ` Steve Grubb
2019-07-16 22:18 ` Casey Schaufler
2019-07-16 22:18 ` Casey Schaufler
2019-07-16 23:13 ` Paul Moore
2019-07-16 23:13 ` Paul Moore
2019-07-16 23:47 ` Casey Schaufler
2019-07-16 23:47 ` Casey Schaufler
2019-07-17 12:14 ` Paul Moore
2019-07-17 12:14 ` Paul Moore
2019-07-17 15:49 ` Casey Schaufler
2019-07-17 15:49 ` Casey Schaufler
2019-07-17 16:23 ` Paul Moore
2019-07-17 16:23 ` Paul Moore
2019-07-17 23:02 ` Casey Schaufler
2019-07-17 23:02 ` Casey Schaufler
2019-07-18 13:10 ` Simon McVittie
2019-07-18 13:10 ` Simon McVittie
2019-07-18 16:13 ` Casey Schaufler
2019-07-18 16:13 ` Casey Schaufler
2019-07-19 12:15 ` Simon McVittie
2019-07-19 12:15 ` Simon McVittie
2019-07-19 16:29 ` Casey Schaufler
2019-07-19 16:29 ` Casey Schaufler
2019-07-19 18:47 ` Simon McVittie
2019-07-19 18:47 ` Simon McVittie
2019-07-19 20:02 ` Dbus and multiple LSMs (was Preferred subj= with multiple LSMs) Casey Schaufler
2019-07-19 20:02 ` Casey Schaufler
2019-07-22 11:36 ` Simon McVittie
2019-07-22 11:36 ` Simon McVittie
2019-07-22 16:04 ` Casey Schaufler
2019-07-22 16:04 ` Casey Schaufler
2019-07-19 21:21 ` Preferred subj= with multiple LSMs Paul Moore
2019-07-19 21:21 ` Paul Moore
2019-07-22 20:50 ` James Morris
2019-07-22 20:50 ` James Morris
2019-07-22 22:01 ` Casey Schaufler
2019-07-22 22:01 ` Casey Schaufler
2019-07-22 22:30 ` Paul Moore
2019-07-22 22:30 ` Paul Moore
2019-07-23 0:11 ` Casey Schaufler
2019-07-23 0:11 ` Casey Schaufler
2019-07-23 14:06 ` Simon McVittie
2019-07-23 14:06 ` Simon McVittie
2019-07-23 17:32 ` Casey Schaufler
2019-07-23 17:32 ` Casey Schaufler
2019-07-23 21:46 ` James Morris
2019-07-23 21:46 ` James Morris
2019-07-16 23:09 ` Paul Moore
2019-07-16 23:09 ` Paul Moore
2019-07-17 4:36 ` James Morris
2019-07-17 4:36 ` James Morris
2019-07-17 12:23 ` Paul Moore
2019-07-17 12:23 ` Paul Moore
2019-07-18 15:01 ` William Roberts
2019-07-18 15:01 ` William Roberts
2019-07-18 18:48 ` Casey Schaufler
2019-07-18 18:48 ` Casey Schaufler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9150011.WShEb2oc6S@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.