From: Casey Schaufler <casey@schaufler-ca.com>
To: Christoph Hellwig <hch@infradead.org>, Eric Paris <eparis@redhat.com>
Cc: linux-nfs@vger.kernel.org, selinux <selinux@tycho.nsa.gov>,
linux-security-module@vger.kernel.org, steved@redhat.com,
jlayton@redhat.com, sds@tycho.nsa.gov, jmorris@namei.org,
casey@schaufler-ca.com, trond.myklebust@fys.uio.no,
chuck.lever@oracle.com, linux-fsdevel@vger.kernel.org
Subject: Re: NFS/LSM: allow NFS to control all of its own mount options
Date: Tue, 19 Feb 2008 15:18:10 -0800 (PST) [thread overview]
Message-ID: <84435.4520.qm@web36603.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080219222408.GB10656@infradead.org>
--- Christoph Hellwig <hch@infradead.org> wrote:
> Please don't introduce a special case for just nfs. All filesystems
> should control their mount options, so please provide some library
> helpers for context= handling and move it into all filesystems that
> can support selinux.
Smack has options that are filesystem independent
(smackfsdef= smackfsroot= smackfsfloor= smackfshat=)
instead of the context= SELinux seems happy with.
Since there is no reason that a file system even
really needs to know what these values are it would
be completely unreasonable to teach every filesystem
about them. The information is completely controlled
and used by the LSM.
Of course, we could use something other than mount options
(vfsctl? sorry - only kidding) to set the LSM specific
information, and that might be the right approach.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2008-02-19 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 21:38 NFS/LSM: allow NFS to control all of its own mount options Eric Paris
[not found] ` <1203457094.2928.113.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-02-19 22:24 ` Christoph Hellwig
2008-02-19 22:36 ` Eric Paris
2008-02-19 23:18 ` Casey Schaufler [this message]
2008-02-20 0:25 ` James Morris
2008-02-20 13:48 ` Stephen Smalley
2008-02-20 10:08 ` Miklos Szeredi
2008-02-20 13:50 ` Stephen Smalley
[not found] ` <1203515410.9902.128.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2008-02-20 13:56 ` Eric Paris
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=84435.4520.qm@web36603.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=chuck.lever@oracle.com \
--cc=eparis@redhat.com \
--cc=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=steved@redhat.com \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox