From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, dustin.kirkland@us.ibm.com
Subject: Re: [PATCH] Rework of IPC auditing
Date: Fri, 31 Mar 2006 14:24:44 -0500 [thread overview]
Message-ID: <200603311424.44064.sgrubb@redhat.com> (raw)
In-Reply-To: <1142018719.13416.91.camel@kirkland1.austin.ibm.com>
On Friday 10 March 2006 14:25, Dustin Kirkland wrote:
> 2) Support for an AUDIT_IPC_NEW_PERM audit message type. This allows
> for separate auxiliary audit records for normal operations on an IPC
> object and permissions changes. Note that the same struct
> audit_aux_data_ipcctl is used and populated, however there are separate
> audit_log_format statements based on the type of the message.
Can we have another name for this record type? I don't want us to get in the
habit of adding "new" to the record type name. Is there something that better
describes its purpose?
-Steve
next parent reply other threads:[~2006-03-31 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1142018719.13416.91.camel@kirkland1.austin.ibm.com>
2006-03-31 19:24 ` Steve Grubb [this message]
2006-03-31 21:13 ` [PATCH] Rework of IPC auditing Dustin Kirkland
2006-04-02 21:07 ` Steve Grubb
2006-04-03 0:05 ` Dustin Kirkland
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=200603311424.44064.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=dustin.kirkland@us.ibm.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