From: Eric Paris <eparis@parisplace.org>
To: Valdis.Kletnieks@vt.edu
Cc: selinux@tycho.nsa.gov, sds@tycho.nsa.gov, jmorris@namei.org,
jbrindle@tresys.com
Subject: Re: [PATCH] SELinux: new /proc/self/attr/ipccreate for expliciteipc object labeling
Date: Fri, 28 Jul 2006 10:12:37 -0400 [thread overview]
Message-ID: <1154095957.5028.79.camel@localhost.localdomain> (raw)
In-Reply-To: <200607272116.k6RLGrFC026797@turing-police.cc.vt.edu>
On Thu, 2006-07-27 at 17:16 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 27 Jul 2006 12:58:49 EDT, Eric Paris said:
>
> > I also decided to leave the name ipccreate even though this does not
> > clearly express that the patch does not cover posix message queues. The
> > only name that seemed descriptive enough was sysvipccreate which just
> > seemed incredibly long for little to no gain. I will address the issue
> > of controlling posix message queue explicit labeling in a future patch.
>
> Will that require another bit?
The thought at the moment does not require another bit.
-Eric
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-07-28 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 19:36 [PATCH] SELinux: new /proc/self/attr/ipccreate for explicite ipc object labeling Eric Paris
2006-07-18 20:01 ` Karl MacMillan
2006-07-18 20:05 ` Stephen Smalley
2006-07-19 14:22 ` Joshua Brindle
2006-07-19 14:42 ` Karl MacMillan
2006-07-19 14:59 ` [PATCH] SELinux: new /proc/self/attr/ipccreate for expliciteipc " Joshua Brindle
2006-07-27 16:58 ` Eric Paris
2006-07-27 18:11 ` Stephen Smalley
2006-07-27 21:16 ` Valdis.Kletnieks
2006-07-28 4:17 ` James Morris
2006-07-28 11:42 ` Stephen Smalley
2006-07-28 14:12 ` Eric Paris [this message]
2006-07-28 4:19 ` James Morris
2006-07-28 5:23 ` Russell Coker
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=1154095957.5028.79.camel@localhost.localdomain \
--to=eparis@parisplace.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jbrindle@tresys.com \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.