linux-kernel - Re: [PATCH 1/1] simplified security.nscapability xattr

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Apr 2016 14:46:57 -0500
From:	Seth Forshee <seth.forshee@...onical.com>
To:	serge.hallyn@...ntu.com
Cc:	linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
	containers@...ts.linux-foundation.org, ebiederm@...ssion.com,
	morgan@...nel.org, luto@...capital.net, keescook@...omium.org,
	jmorris@...ei.org
Subject: Re: [PATCH 1/1] simplified security.nscapability xattr

On Fri, Apr 22, 2016 at 12:26:33PM -0500, serge.hallyn@...ntu.com wrote:
> From: Serge Hallyn <serge.hallyn@...ntu.com>
> 
> This can only be set by root in his own namespace, and will
> only be respected by namespaces with that same root kuid
> mapped as root, or namespaces descended from it.
> 
> This allows a simple setxattr to work, allows tar/untar to
> work, and allows us to tar in one namespace and untar in
> another while preserving the capability, without risking
> leaking privilege into a parent namespace.
> 
> Signed-off-by: Serge Hallyn <serge.hallyn@...ntu.com>

Seems like the simplest possible design which meets the requirements.

Acked-by: Seth Forshee <seth.forshee@...onical.com>