All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Eric Paris <eparis@parisplace.org>,
	selinux@tycho.nsa.gov, kmacmillan@tresys.com, jmorris@namei.org,
	Michael LeMay <mdlemay@epoch.ncsc.mil>
Subject: Re: [PATCH] repost: new sockcreate interface to specify context of socket when they are created
Date: Wed, 21 Jun 2006 16:23:00 -0400	[thread overview]
Message-ID: <1150921381.18657.170.camel@sgc> (raw)
In-Reply-To: <1150919411.27531.89.camel@moss-spartans.epoch.ncsc.mil>

On Wed, 2006-06-21 at 15:50 -0400, Stephen Smalley wrote:
> On Wed, 2006-06-21 at 15:46 -0400, Christopher J. PeBenito wrote:
> > On Wed, 2006-06-21 at 12:03 -0400, Stephen Smalley wrote:
> > > On Wed, 2006-06-21 at 11:08 -0400, Eric Paris wrote:
> > > > Below is a patch to add a new /proc/self/attr/sockcreate
> > [cut]
> > > /proc/self/attr/keycreate is in -mm, so this patch won't apply relative
> > > to it.  Permission definition also has to be regenerated relative to the
> > > keycreate refpolicy patch, as that took the same permission slot.
> > 
> > I'm going to need a patch for refpolicy that has the the final ordering
> > of permissions with key and sockcreate patches.  I haven't added the key
> > class at all yet since I have been waiting for the perm set to finalize.
> 
> Apply the key+keycreate patch first.  sockcreate refpolicy patch has to
> be re-based and re-submitted, but the kernel patch has already been
> re-based and submitted.

Is the one from June 2nd the right one ([PATCH] refpolicy: Kernel access
key retention policy support) to start, and then the one from yesterday
that has setkeycreate?

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150



--
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.

  reply	other threads:[~2006-06-21 20:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 15:08 [PATCH] repost: new sockcreate interface to specify context of socket when they are created Eric Paris
2006-06-21 15:37 ` James Morris
2006-06-21 15:54   ` Eric Paris
2006-06-21 16:08     ` Stephen Smalley
2006-06-21 16:03 ` Stephen Smalley
2006-06-21 16:22   ` James Morris
2006-06-21 16:57     ` James Morris
2006-06-21 19:46   ` Christopher J. PeBenito
2006-06-21 19:50     ` Stephen Smalley
2006-06-21 20:23       ` Christopher J. PeBenito [this message]
2006-06-21 20:25         ` Michael LeMay
2006-06-21 21:07           ` Christopher J. PeBenito
2006-06-21 21:24             ` Michael LeMay

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=1150921381.18657.170.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=kmacmillan@tresys.com \
    --cc=mdlemay@epoch.ncsc.mil \
    --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.