lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 7 Apr 2012 22:15:27 -0700 From: "\"Eric W. Beiderman" <ebiederm@...ssion.com> To: <linux-kernel@...r.kernel.org> Cc: <linux-fsdevel@...r.kernel.org>, <linux-security-module@...r.kernel.org>, Linux Containers <containers@...ts.linux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Al Viro <viro@...IV.linux.org.uk>, Cyrill Gorcunov <gorcunov@...nvz.org>, "Eric W. Biederman" <ebiederm@...ssion.com> Subject: [PATCH 31/43] userns: Teach inode_capable to understand inodes whose uids map to other namespaces. From: Eric W. Biederman <ebiederm@...ssion.com> Signed-off-by: Eric W. Biederman <ebiederm@...ssion.com> --- kernel/capability.c | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/kernel/capability.c b/kernel/capability.c index cc5f071..493d972 100644 --- a/kernel/capability.c +++ b/kernel/capability.c @@ -429,12 +429,14 @@ bool nsown_capable(int cap) * targeted at it's own user namespace and that the given inode is owned * by the current user namespace or a child namespace. * - * Currently inodes can only be owned by the initial user namespace. + * Currently we check to see if an inode is owned by the current + * user namespace by seeing if the inode's owner maps into the + * current user namespace. * */ bool inode_capable(const struct inode *inode, int cap) { struct user_namespace *ns = current_user_ns(); - return ns_capable(ns, cap) && (ns == &init_user_ns); + return ns_capable(ns, cap) && kuid_has_mapping(ns, inode->i_uid); } -- 1.7.2.5 -- 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