From: Glenn Faden <Glenn.Faden@sun.com>
To: Peter Staubach <staubach@redhat.com>
Cc: Spencer Shepler <shepler@storspeed.com>,
"David P. Quigley" <dpquigl@tycho.nsa.gov>,
labeled-nfs@linux-nfs.org, nfs-discuss@opensolaris.org,
nfsv4@ietf.org, selinux@tycho.nsa.gov
Subject: Re: [nfsv4] New MAC label support Internet Draft posted to IETF website
Date: Fri, 23 Jan 2009 13:59:44 -0800 [thread overview]
Message-ID: <497A3DD0.3030406@sun.com> (raw)
In-Reply-To: <497A02A0.9070405@redhat.com>
Sun is also positive about David's proposal although we currently don't
depend on it.
Labeled NFS services are currently provided by Solaris Trusted
Extensions, without relying on NFS protocol extensions. Instead, Trusted
Extensions uses the labels of the network endpoints to determine the
labels of the underlying clients and servers. When acting as an NFS
server, Trusted Extensions sends packets at the same label as the
underlying exported filesystem. These endpoint labels are then
implicitly used to enforce mount policy restrictions by the NFS client
and server code in the kernel. A restriction of this implementation is
that all files in a NFS mounted filesystem must have the same label.
In order for Solaris to support per-file labeling we will need NFS
protocol extensions similar to what David has proposed.
--Glenn
Peter Staubach wrote:
> Spencer Shepler wrote:
>>
>> As David suggests, the NFSv4 working group is positive about this
>> work but until now, the show of specific interest within the NFSv4
>> working group
>> has been very minimal. If this work is to be added to the working
>> group's
>> charter, there must be a show of interest. This can be as simple as an
>> email to the nfsv4@ietf.org alias stating interest and brief description
>> of need/use. This will demonstrate to the area director that work is
>> occurring and it is worthwhile to have the NFSv4 WG undertake the
>> work.
>>
>> So, please speak up, join the nfsv4 WG alias and participate as
>> interest and need declares.
>
> I will start, I guess.
>
> We, Red Hat, are looking at this work as enabling some fundamental
> technologies for our virtual offerings. We need the ability to
> run SELinux over NFS mounted file systems and the current NFSv4[.1]
> support is not sufficient to do it.
>
> Thanx...
>
> ps
>
> --
> 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.
--
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-01-23 21:59 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 19:16 New MAC label support Internet Draft posted to IETF website David P. Quigley
[not found] ` <54E18340-3542-4AB4-843E-E92A67B709A7@storspeed.com>
2009-01-23 17:47 ` [nfsv4] " Peter Staubach
2009-01-23 21:59 ` Glenn Faden [this message]
2009-01-23 19:07 ` [Labeled-nfs] " Kevin L. Smith
[not found] ` <33B70CB9-5260-419A-98CF-94847F829570@nokia.com>
2009-01-28 1:17 ` Jarrett Lu
2009-02-09 22:24 ` Peter Staubach
2009-02-11 23:47 ` David P. Quigley
2009-02-12 1:07 ` [Labeled-nfs] " James Morris
2009-02-12 15:36 ` [nfsv4] " Nicolas Williams
2009-02-12 20:00 ` David P. Quigley
2009-02-12 20:11 ` Nicolas Williams
2009-02-17 16:50 ` David P. Quigley
2009-02-17 17:00 ` Nicolas Williams
2009-02-12 19:45 ` David P. Quigley
2009-02-12 15:22 ` [nfsv4] " Nicolas Williams
2009-03-12 16:08 ` David P. Quigley
2009-03-12 17:20 ` Peter Staubach
2009-03-25 8:52 ` Jarrett Lu
2009-03-25 16:33 ` [nfsv4] " Nicolas Williams
2009-03-26 9:25 ` Jarrett Lu
2009-03-26 15:09 ` Nicolas Williams
2009-03-26 22:03 ` Jarrett Lu
2009-03-27 0:11 ` Nicolas Williams
2009-03-27 12:55 ` [Labeled-nfs] " Stephen Smalley
2009-03-27 13:22 ` Stephen Smalley
2009-03-27 17:03 ` Jarrett Lu
2009-03-27 17:26 ` [nfsv4] [Labeled-nfs] " Nicolas Williams
2009-03-27 18:56 ` Jarrett Lu
2009-03-27 22:04 ` Nicolas Williams
2009-03-30 17:37 ` Stephen Smalley
2009-03-30 18:30 ` Jarrett Lu
2009-03-30 20:01 ` Nicolas Williams
2009-03-30 20:03 ` Nicolas Williams
2009-03-30 21:14 ` Stephen Smalley
2009-03-31 5:59 ` Jarrett Lu
2009-03-31 18:28 ` Nicolas Williams
2009-04-01 3:33 ` Jarrett Lu
2009-04-01 6:58 ` [Labeled-nfs] [nfsv4] " James Morris
2009-04-01 8:09 ` Jarrett Lu
2009-04-01 9:49 ` James Morris
2009-04-01 17:50 ` [nfsv4] [Labeled-nfs] " Nicolas Williams
2009-04-02 23:43 ` Jarrett Lu
2009-03-31 3:07 ` Casey Schaufler
2009-03-31 14:47 ` Paul Moore
2009-04-01 7:46 ` Jarrett Lu
2009-04-01 16:46 ` Paul Moore
2009-04-02 15:24 ` Nicolas Williams
2009-04-02 22:35 ` Paul Moore
2009-04-03 4:42 ` Nicolas Williams
2009-04-03 18:08 ` Joy Latten
2009-04-03 1:21 ` Jarrett Lu
2009-04-07 21:30 ` Paul Moore
2009-03-31 18:34 ` Nicolas Williams
2009-04-01 3:42 ` Casey Schaufler
2009-03-28 3:33 ` [Labeled-nfs] [nfsv4] " Casey Schaufler
2009-03-28 5:16 ` Glenn Faden
2009-03-28 5:52 ` Casey Schaufler
2009-03-27 22:09 ` Nicolas Williams
2009-03-30 16:51 ` Stephen Smalley
2009-03-30 20:05 ` 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=497A3DD0.3030406@sun.com \
--to=glenn.faden@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 \
--cc=shepler@storspeed.com \
--cc=staubach@redhat.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.