All of lore.kernel.org
 help / color / mirror / Atom feed
From: paul.moore@hp.com (Paul Moore)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [RFC] drop nodecons
Date: Fri, 9 Jan 2009 16:11:21 -0500	[thread overview]
Message-ID: <200901091611.22030.paul.moore@hp.com> (raw)
In-Reply-To: <1231508032.20122.3.camel@gorn>

On Friday 09 January 2009 8:33:49 am Christopher J. PeBenito wrote:
> On Thu, 2009-01-08 at 10:45 -0500, Paul Moore wrote:
> > On Thursday 08 January 2009 9:17:11 am Stephen Smalley wrote:
> > > On Wed, 2009-01-07 at 17:20 -0500, Paul Moore wrote:
> > > > The next step is to get semanage to label network nodes (or fix
> > > > it if it is broken).
> > >
> > > semanage node support exists, but might not correctly handle
> > > conflicting/overlapping definitions between the base policy and
> > > local customizations.  See prior discussion on Adding local
> > > nodecon's through semanage on selinux list.
> >
> > Yep, I've still got that thread marked in my inbox as something to
> > revisit.  It will grow more important once we enable the network
> > peer controls policy capability (Chris, thoughts/comments on the
> > patch I posted regardint that?).
>
> I'm not ready to drop the protocol-specific interfaces.  Refpolicy
> still supports back to RHEL4, so the granularity of the original
> networking controls is still important.

Okay fair enough.  Let me know what you think about the patch I 
submitted to enable the network_peer_controls policy capability; I'm 
really hoping that we can enable this for F11.

-- 
paul moore
linux @ hp

  reply	other threads:[~2009-01-09 21:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 15:25 [refpolicy] [RFC] drop nodecons Christopher J. PeBenito
2009-01-07 19:21 ` Paul Moore
2009-01-07 20:24   ` Christopher J. PeBenito
2009-01-07 22:20     ` Paul Moore
2009-01-08 14:17       ` Stephen Smalley
2009-01-08 15:45         ` Paul Moore
2009-01-09 13:33           ` Christopher J. PeBenito
2009-01-09 21:11             ` Paul Moore [this message]
2009-01-12 15:34               ` Chris PeBenito
2009-01-14 16:09                 ` Paul Moore

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=200901091611.22030.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=refpolicy@oss.tresys.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 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.