From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: "Paul Moore" <paul.moore@hp.com>
Cc: "Stephen Smalley" <sds@tycho.nsa.gov>,
"Eric Paris" <eparis@parisplace.org>,
"Daniel J Walsh" <dwalsh@redhat.com>, <selinux@tycho.nsa.gov>
Subject: Re: Enabling policy capabilities
Date: Fri, 18 Apr 2008 10:21:27 -0400 [thread overview]
Message-ID: <1208528487.1548.59.camel@gorn> (raw)
In-Reply-To: <200804101001.23288.paul.moore@hp.com>
On Thu, 2008-04-10 at 10:01 -0400, Paul Moore wrote:
> On Thursday 10 April 2008 9:38:39 am Stephen Smalley wrote:
> > Where do we stand on actually enabling policy capabilities in policy
> > so that people can start using newer features that depend on them?
> >
> > I've definitely seen patches adding permissions for the peer checks,
> > so is there anything preventing us from trying to enable
> > network_peer_controls in policy and seeing what breaks (after Fedora
> > 9 at this point, I suppose - unfortunate that we didn't enable it
> > sooner)?
>
> I still owe Chris an updated set of patches for refpolicy to put all the
> right unlabeled checks in place for the new peer controls. There have
> been lots of patches on the lists but none have been right, yet :)
>
> Once I get the 2.6.26 patches straightened out I'm going to work on
> those.
I added a policy_capabilities file with the two existing caps commented
out.
--
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.
next prev parent reply other threads:[~2008-04-18 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 13:38 Enabling policy capabilities Stephen Smalley
2008-04-10 14:01 ` Paul Moore
2008-04-18 14:21 ` Christopher J. PeBenito [this message]
2008-04-10 16:03 ` Daniel J Walsh
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=1208528487.1548.59.camel@gorn \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=eparis@parisplace.org \
--cc=paul.moore@hp.com \
--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.