From: Christoph Lameter <cl@linux.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Serge Hallyn <serge.hallyn@canonical.com>,
Jonathan Corbet <corbet@lwn.net>,
Aaron Jones <aaronmdjones@gmail.com>,
LSM List <linux-security-module@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linuxfoundation.org>,
"Andrew G. Morgan" <morgan@kernel.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Austin S Hemmelgarn <ahferroin7@gmail.com>,
Markku Savela <msa@moth.iki.fi>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Linux API <linux-api@vger.kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] capabilities: Ambient capability set V2
Date: Sat, 7 Mar 2015 09:09:05 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.11.1503070907330.15173@gentwo.org> (raw)
In-Reply-To: <20150306200838.GA29198@mail.hallyn.com>
On Fri, 6 Mar 2015, Serge E. Hallyn wrote:
> > I think that's right. fI doesn't set pI.
>
> Right. The idea is that for the running binary to get capability x in its
> pP, its privileged ancestor must have set x in pI, and the binary itself
> must be trusted with x in fI.
The ancestor here is ambient_test and when it is run pI will not be set
despite the cap setting.
Therefore anything is spawns cannot have the inheritance bits set either.
This plainly does not make any sense whatsoever. If this is so as it seems
to be then we should be able to remove the inheritance bits because they
have no effect.
next prev parent reply other threads:[~2015-03-07 15:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 22:14 [PATCH] capabilities: Ambient capability set V2 Christoph Lameter
2015-03-01 4:44 ` Serge E. Hallyn
2015-03-02 15:43 ` Christoph Lameter
2015-03-01 23:33 ` Serge E. Hallyn
2015-03-05 15:26 ` Christoph Lameter
2015-03-05 17:13 ` Serge E. Hallyn
2015-03-05 18:41 ` Christoph Lameter
2015-03-05 23:07 ` Andy Lutomirski
2015-03-06 15:47 ` Christoph Lameter
2015-03-06 15:50 ` Christoph Lameter
2015-03-06 16:34 ` Serge E. Hallyn
2015-03-06 18:53 ` Christoph Lameter
2015-03-06 19:02 ` Andy Lutomirski
2015-03-06 20:08 ` Serge E. Hallyn
2015-03-07 15:09 ` Christoph Lameter [this message]
2015-03-07 21:35 ` Serge E. Hallyn
2015-03-09 12:05 ` Christoph Lameter
2015-03-09 14:36 ` Serge E. Hallyn
[not found] ` <CALQRfL4uG2v7SJWZhN2o=ARnSNLR9JAX6MMsCCsGaAz6JcZTsA@mail.gmail.com>
2015-03-10 15:47 ` Christoph Lameter
2015-03-07 15:06 ` Christoph Lameter
2015-03-07 21:35 ` Serge E. Hallyn
2015-03-14 19:04 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.11.1503070907330.15173@gentwo.org \
--to=cl@linux.com \
--cc=aaronmdjones@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=akpm@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=morgan@kernel.org \
--cc=msa@moth.iki.fi \
--cc=mtk.manpages@gmail.com \
--cc=serge.hallyn@canonical.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).