public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: "Dustin Kirkland" <dustin.kirkland@gmail.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] Rework of IPC auditing
Date: Fri, 31 Mar 2006 15:13:44 -0600	[thread overview]
Message-ID: <d9c105ea0603311313xf804639lfdbc8a9eb2773c2@mail.gmail.com> (raw)
In-Reply-To: <200603311424.44064.sgrubb@redhat.com>

On 3/31/06, Steve Grubb <sgrubb@redhat.com> wrote:
> 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?

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.


:-Dustin

  reply	other threads:[~2006-03-31 21:13 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 [this message]
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=d9c105ea0603311313xf804639lfdbc8a9eb2773c2@mail.gmail.com \
    --to=dustin.kirkland@gmail.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