From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io0-f172.google.com ([209.85.223.172]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZfSRp-0004rI-Cm for linux-mtd@lists.infradead.org; Fri, 25 Sep 2015 12:49:57 +0000 Received: by ioii196 with SMTP id i196so109524488ioi.3 for ; Fri, 25 Sep 2015 05:49:36 -0700 (PDT) Date: Fri, 25 Sep 2015 07:49:24 -0500 From: Seth Forshee To: "Eric W. Biederman" Cc: Alexander Viro , Serge Hallyn , James Morris , "Serge E. Hallyn" , Andy Lutomirski , linux-fsdevel@vger.kernel.org, linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org Subject: Re: [PATCH v4 4/7] fs: Limit file caps to the user namespace of the super block Message-ID: <20150925124924.GB104990@ubuntu-hedt> References: <1443039368-55445-1-git-send-email-seth.forshee@canonical.com> <1443039368-55445-5-git-send-email-seth.forshee@canonical.com> <87fv23o4vs.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87fv23o4vs.fsf@x220.int.ebiederm.org> List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Sep 24, 2015 at 04:59:35PM -0500, Eric W. Biederman wrote: > Seth Forshee writes: > > > Capability sets attached to files must be ignored except in the > > user namespaces where the mounter is privileged, i.e. s_user_ns > > and its descendants. Otherwise a vector exists for gaining > > privileges in namespaces where a user is not already privileged. > > > > Add a new helper function, in_user_ns(), to test whether a user > > namespace is the same as or a descendant of another namespace. > > Use this helper to determine whether a file's capability set > > should be applied to the caps constructed during exec. > > No issues with this but given that we always pass current_user_ns() > we may want to simplify the users of in_user_ns by renaming it > current_in_user_ns() and hard codeing current_user_ns(). Sure, if that's what you prefer then I'll change it. Seth