[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2213.1434646275@warthog.procyon.org.uk>
Date: Thu, 18 Jun 2015 17:51:15 +0100
From: David Howells <dhowells@...hat.com>
To: Stephen Smalley <sds@...ho.nsa.gov>
Cc: dhowells@...hat.com, viro@...iv.linux.org.uk, miklos@...redi.hu,
linux-fsdevel@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-unionfs@...r.kernel.org, linux-kernel@...r.kernel.org,
Paul Moore <paul@...l-moore.com>,
SELinux <selinux@...ho.nsa.gov>
Subject: Re: [PATCH 5/8] SELinux: Stub in copy-up handling
Stephen Smalley <sds@...ho.nsa.gov> wrote:
> I'm not sure we never want to copy up the SELinux attribute. See my
> other email about ecryptfs and supporting per-file labeling and
> consistent access control over the upper and lower inodes.
Yes. That's why there are two operations. inode_copy_up() should set the
label appropriately and inode_copy_up_xattr() should prevent the label set by
inode_copy_up() from being clobbered.
Note that inode_copy_up() has access to the lower file label and can perform
some sort of incantation to transmute it before applying it.
David
--
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