linux-kernel - Re: [capabilities] Allow normal inheritance for a configurable set of capabilities

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.DEB.2.11.1502031117100.6368@gentwo.org>
Date:	Tue, 3 Feb 2015 11:18:11 -0600 (CST)
From:	Christoph Lameter <cl@...ux.com>
To:	"Serge E. Hallyn" <serge@...lyn.com>
cc:	Serge Hallyn <serge.hallyn@...ntu.com>,
	Serge Hallyn <serge.hallyn@...onical.com>,
	Andy Lutomirski <luto@...capital.net>,
	Jonathan Corbet <corbet@....net>,
	Aaron Jones <aaronmdjones@...il.com>, Ted Ts'o <tytso@....edu>,
	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, akpm@...uxfoundation.org,
	morgan@...nel.org
Subject: Re: [capabilities] Allow normal inheritance for a configurable set
 of capabilities

On Tue, 3 Feb 2015, Serge E. Hallyn wrote:

> We've currently got two proposals.  (Three includig yours;  but I explained my
> problem with yours earlier this morning -  do appreciate the proposal and
> the patch though, really, thanks)  It's worth digging into the details of
> each, but if they end up complicating things then perhaps "dropping
> capabilities and going with something new" ought to be another proposal.

Ok that is about the binding to a person and executable?

So you think there should be a cap_inheritable mask settable in the caps
of each file.

--
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/