From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <stephen.smalley@gmail.com>
Cc: Eric Paris <eparis@redhat.com>,
penguin-kernel@i-love.sakura.ne.jp, selinux@tycho.nsa.gov,
sds@tycho.nsa.gov, jmorris@namei.org,
linux-security-module@vger.kernel.org, viro@zeniv.linux.org.uk,
hch@lst.de, Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [RFC PATCH 1/2] fs/vfs/security: pass last path component to LSM on inode creation
Date: Tue, 07 Dec 2010 06:58:38 -0800 [thread overview]
Message-ID: <4CFE4B9E.3080408@schaufler-ca.com> (raw)
In-Reply-To: <AANLkTinm_Or+G=BjOU7Tdher-6YnOZXdtb43nGX4N+Et@mail.gmail.com>
On 12/7/2010 5:43 AM, Stephen Smalley wrote:
> ...
> The only real question for this particular patch IMHO is whether the
> changes being made here are sensible from a vfs and fs point of view.
> Most of your comments seem more directed at whether or not SELinux
> should be extended in this manner (i.e. the 2nd patch), and that's a
> question for the SELinux developers, who have already come to
> consensus on the matter.
I will accept that the changes are acceptable to the SELinux
community and that the proposed behavior is perceived as
beneficial within that community.
One of the concerns that has traditionally been raised when new
LSM hooks or changes to existing hooks are proposed is that of
generality. I can think of a number of ways in which the final
component of a pathname could be used to make access control
decisions, but I would not expect to be using them myself. Who
else might you expect to make use of this LSM "enhancement", or
is this something that only SELinux is ever going to want? Is
the component something the LSM should be providing in general,
or is this the only case in which it makes sense?
I think that the LSM interfaces are awfully inconsistent and
quite arbitrary, and that a little bit of consideration about
the possibility of avoiding taking it even further in that
direction is in order, especially when a change is in a fuzzy
area that has been contentious in the past. I remember the
issues that were raised when the AppArmor folks proposed
LSM interface changes, and while the changes proposed today
lack the problems those changes did the same issues need to
be raised and addressed.
In the end, I don't mind an additional parameter I'll not be
using in Smack if it is generally useful.
--
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:[~2010-12-07 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 21:45 [RFC PATCH 1/2] fs/vfs/security: pass last path component to LSM on inode creation Eric Paris
2010-12-03 21:45 ` [RFC PATCH 2/2] SELinux: Use dentry name in new object labeling Eric Paris
2010-12-04 4:20 ` [RFC PATCH 1/2] fs/vfs/security: pass last path component to LSM on inode creation Casey Schaufler
2010-12-04 21:34 ` Eric Paris
2010-12-05 7:38 ` Casey Schaufler
2010-12-06 14:32 ` Daniel J Walsh
2010-12-06 23:32 ` Kyle Moffett
2010-12-07 13:43 ` Stephen Smalley
2010-12-07 14:58 ` Casey Schaufler [this message]
2010-12-07 16:11 ` Stephen Smalley
2010-12-07 16:56 ` Casey Schaufler
2010-12-07 17:34 ` Stephen Smalley
2010-12-07 18:00 ` Casey Schaufler
2010-12-08 14:25 ` Kyle Moffett
2010-12-08 14:49 ` Casey Schaufler
2010-12-08 19:04 ` Daniel J Walsh
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=4CFE4B9E.3080408@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=eparis@redhat.com \
--cc=hch@lst.de \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=stephen.smalley@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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.