[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.1003030855400.14492@tundra.namei.org>
Date: Wed, 3 Mar 2010 09:01:22 +1100 (EST)
From: James Morris <jmorris@...ei.org>
To: Joel Becker <Joel.Becker@...cle.com>
cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
David Woodhouse <dwmw2@...radead.org>,
Mark Fasheh <mfasheh@...e.com>, Alex Elder <aelder@....com>,
Chris Mason <chris.mason@...cle.com>,
a.gruenbacher@...puter.org
Subject: Re: [PATCH 2/2] ocfs2: ensure trusted xattrs are not returned to
unprivileged users via listxattr
On Tue, 2 Mar 2010, Joel Becker wrote:
> On Tue, Mar 02, 2010 at 07:02:22PM +1100, James Morris wrote:
> > Ensure that trusted xattrs are not returned to unprivileged users
> > via listxattr, in keeping with several other implmentations, such
> > as ext3.
> >
> > Signed-off-by: James Morris <jmorris@...ei.org>
>
> If this is the standard expectation, why not lift it up into the vfs?
The VFS doesn't know what's in the listxattr list. When using generic
xattr handlers for synthetic xattrs, it's easy to determine the xattr
namespace (each namespace has a handler), although on-disk xattrs need to
be read from disk to determine if they're in the trusted namespace.
The VFS could possibly modify the listxattr results after the fact,
although it's very ugly, and it would not be able to correctly handle size
probes, where the VFS only sees a total size value from the FS.
- James
--
James Morris
<jmorris@...ei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists