From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Russ Housley <housley@vigilsec.com>
Cc: Santosh Chokhani <SChokhani@cygnacom.com>,
saag@ietf.org, labeled-nfs@linux-nfs.org, selinux@tycho.nsa.gov,
nfsv4@ietf.org, nfs-discuss@opensolaris.org
Subject: Re: [saag] Common labeled security (comment on CALIPSO, labeled NFSv4)
Date: Fri, 3 Apr 2009 11:51:44 -0500 [thread overview]
Message-ID: <20090403165143.GC1500@Sun.COM> (raw)
In-Reply-To: <20090403164522.DEA9A9A4739@odin.smetech.net>
On Fri, Apr 03, 2009 at 12:44:30PM -0400, Russ Housley wrote:
> I really do not have time to write about all of my
> concerns. However, once you get beyond the basic classifications,
> the SPIF model breaks. They are markings that are only to be known
> to people that have the clearance for those markings, this leads to a
> SPIF distribution nightmare, as a subset of the real SPIF must be
> given out based on access (or not) to various compartments and
> such. It just does not scale.
I'm aware of the fact that labels can themselves be labeled. But I
don't think that implies that we can't make a SPIF-like solution scale.
Peers that have access to different subsets of the policy should still
be able to interop if care is taken to specify what happens when a node
sees a label that falls outside its policy subset, and provided, of
course, that the peers can agree that they have subsets of the *same*
master policy. Peers can check whether they do have subsets of the
*same* master policy by exchanging [for each DOI to both] a master
policy URI that includes a version number.
Nico
--
--
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:[~2009-04-03 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 15:44 Common labeled security (comment on CALIPSO, labeled NFSv4) Nicolas Williams
[not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FF82@scygexch1.cygnacom.com>
2009-04-03 15:42 ` [saag] " Nicolas Williams
[not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FF9E@scygexch1.cygnacom.com>
2009-04-03 17:36 ` Nicolas Williams
[not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FFAF@scygexch1.cygnacom.com>
2009-04-03 19:18 ` Nicolas Williams
[not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FFBE@scygexch1.cygnacom.com>
2009-04-03 19:57 ` Nicolas Williams
[not found] ` <49D80922.9050700@ieca.com>
2009-04-06 15:11 ` Nicolas Williams
[not found] ` <20090403164522.DEA9A9A4739@odin.smetech.net>
2009-04-03 16:51 ` Nicolas Williams [this message]
[not found] ` <9C2457A4-328A-4A68-A9D2-6E4B5544078D@Isode.com>
[not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FFE0@scygexch1.cygnacom.com>
[not found] ` <B8FB99E8-17AA-4D4B-A309-8AF79838A304@Isode.com>
[not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FFE9@scygexch1.cygnacom.com>
2009-04-06 15:16 ` Nicolas Williams
[not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48AA0032@scygexch1.cygnacom.com>
2009-04-06 16:22 ` Nicolas Williams
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=20090403165143.GC1500@Sun.COM \
--to=nicolas.williams@sun.com \
--cc=SChokhani@cygnacom.com \
--cc=housley@vigilsec.com \
--cc=labeled-nfs@linux-nfs.org \
--cc=nfs-discuss@opensolaris.org \
--cc=nfsv4@ietf.org \
--cc=saag@ietf.org \
--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.