From: Stephen Smalley <sds@tycho.nsa.gov>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Jarrett Lu <Jarrett.Lu@sun.com>,
dpquigl@tycho.nsa.gov, labeled-nfs@linux-nfs.org,
nfs-discuss@opensolaris.org, selinux@tycho.nsa.gov,
nfsv4@ietf.org
Subject: Re: [nfsv4] my thoughts on how Labeled NFSv4 draft should move forward
Date: Mon, 13 Apr 2009 09:19:17 -0400 [thread overview]
Message-ID: <1239628757.6129.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20090410201718.GB1500@Sun.COM>
On Fri, 2009-04-10 at 15:17 -0500, Nicolas Williams wrote:
> After that long thread on SAAG and a subsequent off-list discussion with
> Casey (plus my reading Smack documentation) I'm almost ready to reach
> the following conclusions:
>
> - We don't need policy agreement for MLS. Servers have all the
> necessary information when comparing labels without reference to a
> policy. However, clients have to be sharing a common MLS policy.
That is too limiting. Think coalitions.
> - For "smart" MLS and Smack servers we need a method by which servers
> can determine the label range/set of client and user principals, but
> this need not be specified in a standard way except where label
> range/set is borne by authentication credentials (Kerberos V ticket
> authorization-data, PKIX cert extensions).
>
> This is already described in my RPCSEC_GSSv3 document.
>
> - For Smack we don't need policy agreement either, but it will be
> useful to distribute common subsets of Smack policy to clients, and
> to prefix labels from local-only sub-policies with a client ID (or
> client DOI, if you wish).
>
> - For DTE I've no idea what to do. Policy agreement seems like a
> flight of fancy for DTE. But *much* more importantly, because the
> process label transitions can span so many labels we simply cannot
> have too smart a server: the server can't meaningfully constrain the
> labels that a user@client can assert, therefore the server must trust
> all client assertions of process DTE labels or none at all.
>
> I.e., for DTE we can only have "dumb" servers.
Why? While it is certainly true that a given client may be authorized
to assert numerous discrete domains, that does not mean that a server
cannot limit a client to a specific set of domains. That can be modeled
via a permission check on a label pair and security class, just like
everything else.
--
Stephen Smalley
National Security Agency
--
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-13 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 21:07 my thoughts on how Labeled NFSv4 draft should move forward Jarrett Lu
2009-04-06 22:08 ` [nfsv4] " Nicolas Williams
2009-04-10 19:43 ` David P. Quigley
2009-04-10 19:43 ` David P. Quigley
2009-04-10 20:17 ` [nfsv4] " Nicolas Williams
2009-04-10 20:38 ` Nicolas Williams
2009-04-14 15:59 ` David P. Quigley
2009-04-14 17:10 ` Nicolas Williams
2009-04-13 13:19 ` Stephen Smalley [this message]
2009-04-13 15:31 ` Nicolas Williams
2009-04-14 4:02 ` Casey Schaufler
2009-04-14 17:26 ` 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=1239628757.6129.5.camel@localhost.localdomain \
--to=sds@tycho.nsa.gov \
--cc=Jarrett.Lu@sun.com \
--cc=Nicolas.Williams@sun.com \
--cc=dpquigl@tycho.nsa.gov \
--cc=labeled-nfs@linux-nfs.org \
--cc=nfs-discuss@opensolaris.org \
--cc=nfsv4@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.