From: Serge Hallyn <serge.hallyn@ubuntu.com>
To: Christoph Lameter <cl@linux.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
Andy Lutomirski <luto@amacapital.net>,
Aaron Jones <aaronmdjones@gmail.com>, "Ted Ts'o" <tytso@mit.edu>,
linux-security-module@vger.kernel.org, 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-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] capabilities: Ambient capability set V1
Date: Mon, 23 Feb 2015 18:15:53 +0000 [thread overview]
Message-ID: <20150223181553.GE25477@ubuntumail> (raw)
In-Reply-To: <alpine.DEB.2.11.1502231049110.21926@gentwo.org>
Quoting Christoph Lameter (cl@linux.com):
> On Mon, 23 Feb 2015, Serge E. Hallyn wrote:
>
> > > I do not see a problem with dropping privilege since the ambient set
> > > is supposed to be preserved across a drop of priviledge.
> >
> > Because you're tricking the program into thinking it has dropped
> > the privilege, when in fact it has not.
>
> So the cap was dropped from the cap perm set but it is still active
> in the ambient set?
Right, and the legacy program doesn't know to check the new set.
next prev parent reply other threads:[~2015-02-23 18:16 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 21:56 [PATCH] capabilities: Ambient capability set V1 Christoph Lameter
2015-02-23 14:58 ` Christoph Lameter
2015-02-23 15:44 ` Andy Lutomirski
2015-02-23 15:53 ` Christoph Lameter
2015-02-23 15:59 ` Andy Lutomirski
2015-02-23 16:41 ` Christoph Lameter
2015-02-23 23:51 ` Andy Lutomirski
2015-02-24 15:48 ` Christoph Lameter
2015-02-23 16:16 ` Serge Hallyn
2015-02-23 16:33 ` Andy Lutomirski
2015-02-23 16:45 ` Serge E. Hallyn
2015-02-23 16:47 ` Christoph Lameter
2015-02-23 16:44 ` Christoph Lameter
2015-02-23 16:46 ` Serge E. Hallyn
2015-02-23 16:50 ` Christoph Lameter
2015-02-23 18:15 ` Serge Hallyn [this message]
2015-02-23 18:27 ` Christoph Lameter
2015-02-24 5:19 ` Serge E. Hallyn
2015-02-24 15:47 ` Serge E. Hallyn
2015-02-24 15:58 ` Christoph Lameter
2015-02-24 16:44 ` Serge Hallyn
2015-02-24 17:28 ` Christoph Lameter
2015-02-25 3:32 ` Serge Hallyn
2015-02-25 20:25 ` Christoph Lameter
2015-02-26 15:35 ` Serge E. Hallyn
2015-02-26 18:28 ` Christoph Lameter
2015-02-26 19:32 ` Serge E. Hallyn
2015-02-26 19:38 ` Andy Lutomirski
2015-02-26 20:16 ` Christoph Lameter
2015-02-26 20:33 ` Serge E. Hallyn
2015-02-26 20:13 ` Christoph Lameter
2015-02-26 20:34 ` Serge E. Hallyn
2015-02-26 20:51 ` Andy Lutomirski
2015-02-26 20:55 ` Serge E. Hallyn
2015-02-26 20:58 ` Andy Lutomirski
2015-02-26 21:19 ` Serge E. Hallyn
2015-02-26 21:29 ` Christoph Lameter
2015-02-26 21:09 ` Christoph Lameter
2015-02-26 21:13 ` Serge E. Hallyn
2015-02-26 21:23 ` Christoph Lameter
2015-02-26 21:32 ` Serge E. Hallyn
2015-02-26 21:37 ` Christoph Lameter
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=20150223181553.GE25477@ubuntumail \
--to=serge.hallyn@ubuntu.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=serge@hallyn.com \
--cc=tytso@mit.edu \
--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