From: Linda Knippers <linda.knippers@hp.com>
To: Klaus Weidner <klaus@atsec.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] IPC_SET_PERM cleanup
Date: Wed, 10 May 2006 13:22:03 -0400 [thread overview]
Message-ID: <4462213B.7000706@hp.com> (raw)
In-Reply-To: <20060510171150.GH31457@w-m-p.com>
> I'm not sure that's really necessary, the type=IPC_SET_PERM already tells
> you that these are new values. How about simply the following:
>
> type=IPC_SET_PERM msg=audit(1146863632.117:98): qbytes=0 iuid=501 igid=0 mode=0
Would you use ouid and ogid in the IPC record? Do we need mode
in the IPC record? We have it in the PATH records.
-- ljk
next prev parent reply other threads:[~2006-05-10 17:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 20:19 [PATCH] IPC_SET_PERM cleanup Linda Knippers
2006-05-05 20:42 ` Steve Grubb
2006-05-05 20:59 ` Linda Knippers
2006-05-09 14:51 ` Klaus Weidner
2006-05-05 21:26 ` Linda Knippers
2006-05-08 18:29 ` Dustin Kirkland
2006-05-08 18:29 ` Dustin Kirkland
2006-05-08 19:06 ` Linda Knippers
2006-05-09 14:59 ` Klaus Weidner
2006-05-09 15:05 ` Steve Grubb
2006-05-09 15:12 ` Linda Knippers
2006-05-09 15:21 ` Steve Grubb
2006-05-09 15:34 ` Linda Knippers
2006-05-09 15:55 ` Steve Grubb
2006-05-09 16:33 ` Klaus Weidner
2006-05-09 17:47 ` Linda Knippers
2006-05-09 18:15 ` Klaus Weidner
2006-05-09 18:27 ` Linda Knippers
2006-05-09 19:11 ` Steve Grubb
2006-05-09 20:10 ` Klaus Weidner
2006-05-09 20:36 ` Klaus Weidner
2006-05-09 20:46 ` Linda Knippers
2006-05-10 14:02 ` Steve Grubb
2006-05-10 16:29 ` Klaus Weidner
2006-05-10 17:02 ` Dustin Kirkland
2006-05-10 17:11 ` Klaus Weidner
2006-05-10 17:22 ` Linda Knippers [this message]
2006-05-10 17:29 ` Steve Grubb
2006-05-10 18:10 ` Klaus Weidner
2006-05-10 17:28 ` Steve Grubb
2006-05-10 18:05 ` Linda Knippers
2006-05-10 18:20 ` Steve Grubb
2006-05-09 15:53 ` Amy Griffis
2006-05-09 15:07 ` 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=4462213B.7000706@hp.com \
--to=linda.knippers@hp.com \
--cc=klaus@atsec.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