From: Joshua Brindle <method@manicmethod.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Todd Miller <Tmiller@tresys.com>, Paul Moore <paul.moore@hp.com>,
selinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>,
"Christopher J. PeBenito" <cpebenito@tresys.com>
Subject: Re: [patch 0/2] policy capability support
Date: Wed, 05 Dec 2007 15:16:59 -0500 [thread overview]
Message-ID: <4757073B.70907@manicmethod.com> (raw)
In-Reply-To: <1196883697.16006.103.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Wed, 2007-12-05 at 14:30 -0500, Todd Miller wrote:
>> Paul Moore wrote:
>>> The discussion for this appears to have gone quiet (at least I
>>> haven't seen anything else on this list). Where do things currently
>>> stand?
>> At this point I'd be OK with requiring equivalence and throwing an error
>> otherwise. I do think that this will result in usability issues that we
>> will have to address once people start using the caps. However, with
>> only
>> a single cap defined so far it is not really possible to know how these
>> will end up being used.
>
> We could try to come up with a solution at least for allowing clean
> upgrades from F8 (w/o any caps) to F9 (likely w/ peer cap defined)
> without requiring manual user intervention for dealing with local
> modules.
>
This was my exact objection to using an intersection or equivalence. IMO
it is incompatible to require all modules to be the same and to also
require upgrades to work without manual intervention.
Do you still think unioning is wrong?
> There are however plenty of other ways in which a policy upgrade can
> break at present.
>
--
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:[~2007-12-05 20:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 18:48 [patch 0/2] policy capability support tmiller
2007-12-05 18:48 ` [patch 1/2] library " tmiller
2007-12-05 18:48 ` [patch 2/2] checkpolicy " tmiller
2007-12-05 19:21 ` [patch 0/2] policy " Paul Moore
2007-12-05 19:30 ` Todd Miller
2007-12-05 19:41 ` Stephen Smalley
2007-12-05 20:16 ` Joshua Brindle [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-12-06 21:38 tmiller
2008-01-08 17:05 ` Paul Moore
2008-01-08 19:01 ` Stephen Smalley
2008-01-08 19:07 ` 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=4757073B.70907@manicmethod.com \
--to=method@manicmethod.com \
--cc=Tmiller@tresys.com \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--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.