From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, Eric Paris <eparis@redhat.com>
Cc: jmorris@namei.org, casey@schaufler-ca.com,
selinux <selinux@tycho.nsa.gov>,
linux-security-module@vger.kernel.org
Subject: Re: How to handle NFS and conflicting mount options
Date: Wed, 5 Mar 2008 09:15:13 -0800 (PST) [thread overview]
Message-ID: <292813.32356.qm@web36605.mail.mud.yahoo.com> (raw)
In-Reply-To: <1204728406.1397.36.camel@moss-spartans.epoch.ncsc.mil>
--- Stephen Smalley <sds@tycho.nsa.gov> wrote:
>
> On Wed, 2008-03-05 at 09:42 -0500, Eric Paris wrote:
> > On Wed, 2008-03-05 at 09:27 -0500, Jeff Layton wrote:
> > > On Wed, 05 Mar 2008 09:11:10 -0500
> > > Eric Paris <eparis@redhat.com> wrote:
> >
> > > > This is going to use the same superblock but the context= needs to the
> > > > same. There is no was to reconcile the 2, so we just reject the second
> > > > mount.
> > > >
> > >
> > > We could just not share superblocks in that case. Maybe add a new
> > > condition to nfs_compare_mount_options()? When that returns 0 now, I
> > > believe we spin off a new superblock.
> >
> > I'll add it to my list of things to look at for .26.
> > nfs_compare_mount_options doesn't have all the data the LSM would need
> > but nfs_compare_super probably does. The selinux code is not going to
> > change in this regard since most FS don't have such a nice 'just use a
> > new one' option and the LSM should make sure it isn't doing things under
> > the covers the user wasn't expecting. Using this feature is not going
> > to clean up the necessity for that little if statement you were looking
> > at but I can probably make NFS and multiple lsm options play nicer
> > together in a future patch.
> >
> > -Eric
> >
> > [pulled from NFS list to just the security people]
> >
> > Does this even make sense? Should we allow:
> >
> > mount -o context=context1 server:/export /mnt/mnt1
> > mount -o context=context2 server:/export /mnt/mnt2
> >
> > Same data different label?
>
> No, that's contrary to the goals of labeled MAC.
Although I've seen people do this in real installations I
agree with Stephen that it is wrong and ought not be allowed.
> > How about
> >
> > mount -o context=context1 server:/export/subdir1 /mnt/mnt1
> > mount -o context=context2 server:/export/subdir2 /mnt/mnt2
> >
> > Here we have the same SB but different data and different labels.
>
> This one would be nice, as it would allow for e.g. different user home
> directories to be mounted at different contexts.
Again, I've seen people do this, but they then allow people to
log onto the server and use it with the security scheme there,
which almost always gives them a way around the restrictions put
in place by the client's mount strategy. So I say that you gain
no value by allowing this.
Casey Schaufler
casey@schaufler-ca.com
--
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.
prev parent reply other threads:[~2008-03-05 17:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 19:42 [PATCH -v2] NFS/LSM: allow NFS to control all of its own mount options Eric Paris
2008-03-03 19:42 ` Eric Paris
2008-03-03 19:38 ` Dave Quigley
2008-03-03 19:38 ` Dave Quigley
[not found] ` <1204573122.14520.90.camel-88+Bj4OksMGWPftkNcioYDMZycKHmlmlfvIqQ387n9k@public.gmane.org>
2008-03-03 20:10 ` Eric Paris
2008-03-03 20:10 ` Eric Paris
2008-03-03 20:10 ` Eric Paris
2008-03-03 19:51 ` Dave Quigley
2008-03-03 19:51 ` Dave Quigley
2008-03-04 22:54 ` James Morris
2008-03-04 22:54 ` James Morris
2008-03-05 13:48 ` Jeff Layton
2008-03-05 14:11 ` Eric Paris
2008-03-05 14:11 ` Eric Paris
[not found] ` <1204726270.3216.196.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-03-05 14:27 ` Jeff Layton
2008-03-05 14:27 ` Jeff Layton
[not found] ` <20080305092758.1bfe9687-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2008-03-05 14:34 ` Eric Paris
2008-03-05 14:34 ` Eric Paris
2008-03-05 14:34 ` Eric Paris
2008-03-05 14:42 ` How to handle NFS and conflicting " Eric Paris
2008-03-05 14:46 ` Stephen Smalley
2008-03-05 14:54 ` Eric Paris
2008-03-05 17:15 ` Casey Schaufler [this message]
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=292813.32356.qm@web36605.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--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.