From: "Serge E. Hallyn" <serge@hallyn.com>
To: Christoph Lameter <cl@linux.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
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: Mon, 9 Mar 2015 09:36:53 -0500 [thread overview]
Message-ID: <20150309143653.GA29594@mail.hallyn.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1503090704230.25725@gentwo.org>
On Mon, Mar 09, 2015 at 07:05:24AM -0500, Christoph Lameter wrote:
> On Sat, 7 Mar 2015, Serge E. Hallyn wrote:
>
> > > The ancestor here is ambient_test and when it is run pI will not be set
> > > despite the cap setting.
> >
> > ambient_test is supposed to set it.
>
> I thought the setcap +i would do it.
>
> So the setcap and setting of the file inheritance bits has no effect on
> pI? When the process starts pI is off despite fI being set?
Correct, pI must be set through capset(). Again, x in fI is saying
that the certain trusted users may have x in pP when they run the
binary; x in pi means that the users may have x in pP when they run
certain files. Other users running the file won't have x in pP, and
the special user running other files won't have x in pP.
next prev parent reply other threads:[~2015-03-09 14:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 22:14 [PATCH] capabilities: Ambient capability set V2 Christoph Lameter
2015-02-26 22:14 ` Christoph Lameter
[not found] ` <alpine.DEB.2.11.1502261612370.8994-gkYfJU5Cukgdnm+yROfE0A@public.gmane.org>
2015-03-01 4:44 ` Serge E. Hallyn
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-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
[not found] ` <CALCETrUVrfPBpb69WFyptzFoJ8Sx4LwhhjirVx=KQ11ofCcwYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-06 15:47 ` Christoph Lameter
2015-03-06 15:47 ` Christoph Lameter
[not found] ` <20150305171326.GA14998-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2015-03-06 15:50 ` Christoph Lameter
2015-03-06 15:50 ` Christoph Lameter
[not found] ` <alpine.DEB.2.11.1503060948460.8207-gkYfJU5Cukgdnm+yROfE0A@public.gmane.org>
2015-03-06 16:34 ` Serge E. Hallyn
2015-03-06 16:34 ` Serge E. Hallyn
2015-03-06 18:53 ` Christoph Lameter
[not found] ` <alpine.DEB.2.11.1503061244130.9804-gkYfJU5Cukgdnm+yROfE0A@public.gmane.org>
2015-03-06 19:02 ` Andy Lutomirski
2015-03-06 19:02 ` Andy Lutomirski
2015-03-06 20:08 ` Serge E. Hallyn
[not found] ` <20150306200838.GA29198-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2015-03-07 15:09 ` Christoph Lameter
2015-03-07 15:09 ` Christoph Lameter
[not found] ` <alpine.DEB.2.11.1503070907330.15173-gkYfJU5Cukgdnm+yROfE0A@public.gmane.org>
2015-03-07 21:35 ` Serge E. Hallyn
2015-03-07 21:35 ` Serge E. Hallyn
2015-03-09 12:05 ` Christoph Lameter
2015-03-09 14:36 ` Serge E. Hallyn [this message]
[not found] ` <CALQRfL4uG2v7SJWZhN2o=ARnSNLR9JAX6MMsCCsGaAz6JcZTsA@mail.gmail.com>
[not found] ` <CALQRfL4uG2v7SJWZhN2o=ARnSNLR9JAX6MMsCCsGaAz6JcZTsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-10 15:47 ` Christoph Lameter
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=20150309143653.GA29594@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=aaronmdjones@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=akpm@linuxfoundation.org \
--cc=cl@linux.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.