From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: tmiller@tresys.com, selinux@tycho.nsa.gov,
method@manicmethod.com, dwalsh@redhat.com, cpebenito@tresys.com,
kmacmillan@mentalrootkit.com
Subject: Re: [patch 0/2] policy capability support
Date: Tue, 8 Jan 2008 14:07:18 -0500 [thread overview]
Message-ID: <200801081407.18490.paul.moore@hp.com> (raw)
In-Reply-To: <1199818897.9393.164.camel@moss-spartans.epoch.ncsc.mil>
On Tuesday 08 January 2008 2:01:37 pm Stephen Smalley wrote:
> On Tue, 2008-01-08 at 12:05 -0500, Paul Moore wrote:
> > On Thursday 06 December 2007 4:38:52 pm tmiller@tresys.com wrote:
> > > Updated policycap patch set based on recent discussion. The
> > > consensus seems to be to only allow policycaps in the base
> > > module. This is now enforced by the checkpolicy/checkmodule
> > > parser.
> >
> > I haven't heard much about this patch lately - what is the current
> > status? I know Stephen had some minor comments but other than that
> > I didn't see any objections ...
>
> It was merged. checkpolicy 2.0.7 and libsepol 2.0.18.
> But you now need a base module re-built with the capabilities
> defined. So we need to get a policy patch that does that if/when we
> are ready to turn on the new networking controls for real.
Great, thanks for the update.
--
paul moore
linux security @ hp
--
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-01-08 19:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 21:38 [patch 0/2] policy capability support tmiller
2007-12-06 21:38 ` [patch 1/2] library " tmiller
2007-12-06 21:38 ` [patch 2/2] checkpolicy " tmiller
2007-12-21 17:30 ` Stephen Smalley
2008-01-08 17:05 ` [patch 0/2] policy " Paul Moore
2008-01-08 19:01 ` Stephen Smalley
2008-01-08 19:07 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-05 18:48 tmiller
2007-12-05 19:21 ` Paul Moore
2007-12-05 19:30 ` Todd Miller
2007-12-05 19:41 ` Stephen Smalley
2007-12-05 20:16 ` Joshua Brindle
2007-12-05 20:34 ` Stephen Smalley
2007-12-05 20:35 ` Joshua Brindle
2007-12-05 20:50 ` Stephen Smalley
2007-12-05 20:56 ` Joshua Brindle
2007-12-06 15:21 ` Stephen Smalley
2007-12-06 16:44 ` Joshua Brindle
2007-12-06 18:08 ` Stephen Smalley
2007-12-06 20:24 ` Todd Miller
2007-12-06 21:24 ` Stephen Smalley
2007-12-06 21:23 ` Joshua Brindle
2007-12-06 21:42 ` Stephen Smalley
2007-12-07 14:47 ` Joshua Brindle
2007-12-07 16:26 ` Stephen Smalley
2007-12-07 21:17 ` Daniel J Walsh
2007-12-07 21:30 ` Joshua Brindle
2007-12-07 21:35 ` Stephen Smalley
2007-12-08 11:53 ` Daniel J Walsh
2007-12-05 21:41 ` Todd Miller
2007-12-06 15:44 ` Christopher J. PeBenito
2007-12-06 16:48 ` Stephen Smalley
2007-12-06 18:34 ` Christopher J. PeBenito
2007-12-06 20:02 ` Stephen Smalley
2007-12-06 20:09 ` Stephen Smalley
2007-12-06 18:50 ` 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=200801081407.18490.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=kmacmillan@mentalrootkit.com \
--cc=method@manicmethod.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=tmiller@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.