From: John Dennis <jdennis@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] Fix acct quoting in audit_log_acct_message())
Date: Tue, 04 Mar 2008 16:21:01 -0500 [thread overview]
Message-ID: <47CDBD3D.7030101@redhat.com> (raw)
In-Reply-To: <1204663403.3216.126.camel@localhost.localdomain>
Eric Paris wrote:
> Can you show some example of which kernels had one thing and which
> kernels another?
These are the encoded audit strings in kernel 2.6.24 (Fedora):
a[0-9]+
comm
cwd
data
dir
exe
key
msg
name
new
old
path
These are the encoded audit strings in kernel 2.6.18 (RHEL-5):
comm
cwd
exe
key
name
new
ocomm
old
path
This is what audit-1.6.5 checks for:
acct
cmd
comm
cwd
exe
file
name
path
watch
This list does not include strings which are not encoded, only those
known to be subject to hexadecimal decoding!
Absolutely none of the above fields should require special table driven
logic in order to read their value as a string.
Just to make life interesting I believe some of these field names appear
in more than one record type.
This is just two OS's. In real deployments a site might be running a
much larger set of OS's all emitting audit data and probably not
capturing the OS version along with the audit data. Every time we have a
new release we compound the problem. Every time a new piece of audit
data is added the problem is compounded. Any patch has the potential to
modify the audit contents.
--
John Dennis <jdennis@redhat.com>
next prev parent reply other threads:[~2008-03-04 21:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 3:50 [PATCH] Fix acct quoting in audit_log_acct_message()) Miloslav Trmac
2008-03-04 15:07 ` John Dennis
2008-03-04 18:10 ` Tomas Mraz
2008-03-04 18:29 ` John Dennis
2008-03-04 19:05 ` Eric Paris
2008-03-05 4:02 ` Valdis.Kletnieks
2008-03-05 13:15 ` Eric Paris
2008-03-04 18:56 ` Steve Grubb
2008-03-04 19:08 ` Miloslav Trmac
2008-03-04 19:28 ` Steve Grubb
2008-03-04 19:15 ` Eric Paris
2008-03-04 20:41 ` John Dennis
2008-03-04 20:29 ` John Dennis
2008-03-04 20:36 ` Tomas Mraz
2008-03-04 20:57 ` John Dennis
2008-03-04 20:43 ` Eric Paris
2008-03-04 20:52 ` Steve Grubb
2008-03-04 21:21 ` John Dennis [this message]
2008-03-04 21:38 ` Steve Grubb
2008-03-04 21:55 ` Eric Paris
2008-03-04 22:03 ` Eric Paris
2008-03-04 22:18 ` Steve Grubb
2008-03-04 22:32 ` John Dennis
2008-03-05 14:11 ` John Dennis
2008-03-04 22:14 ` Steve Grubb
2008-03-04 22:21 ` Eric Paris
2008-03-04 23:00 ` Steve Grubb
2008-03-09 18:36 ` Steve Grubb
-- strict thread matches above, loose matches on Subject: below --
2008-03-05 13:55 Miloslav Trmac
2008-03-05 14:11 ` Tomas Mraz
2008-03-05 15:04 ` John Dennis
2008-03-05 15:21 ` Tomas Mraz
2008-03-05 15:29 ` Steve Grubb
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=47CDBD3D.7030101@redhat.com \
--to=jdennis@redhat.com \
--cc=eparis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox