From: Dustin Kirkland <dustin.kirkland@us.ibm.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] Rework of IPC auditing
Date: Sun, 02 Apr 2006 19:05:33 -0500 [thread overview]
Message-ID: <1144022733.3854.0.camel@localhost.localdomain> (raw)
In-Reply-To: <200604021707.33409.sgrubb@redhat.com>
On Sun, 2006-04-02 at 17:07 -0400, Steve Grubb wrote:
> On Friday 31 March 2006 16:13, Dustin Kirkland wrote:
> > I know we discussed on IRC, but for everyone's benefit, we're going to
> > call this record type AUDIT_IPC_SET_PERM and the function
> > audit_ipc_set_perm(), as it's called in each of the IPC_SET operations
> > on the ipc objects.
>
> Hi,
>
> I've reworked your rework patch so that it applies to the end of the current
> stack of patches. Its included below. Please review for any serious omissions
> or gaffs.
Steve-
I've reviewed and it looks good. +1.
:-Dustin
prev parent reply other threads:[~2006-04-03 0:05 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 ` [PATCH] Rework of IPC auditing Steve Grubb
2006-03-31 21:13 ` Dustin Kirkland
2006-04-02 21:07 ` Steve Grubb
2006-04-03 0:05 ` Dustin Kirkland [this message]
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=1144022733.3854.0.camel@localhost.localdomain \
--to=dustin.kirkland@us.ibm.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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