From: Christoph Lameter <cl@linux.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Serge Hallyn <serge.hallyn@ubuntu.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
Aaron Jones <aaronmdjones@gmail.com>, "Ted Ts'o" <tytso@mit.edu>,
LSM List <linux-security-module@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-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux API <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 10:47:01 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.11.1502231046080.21888@gentwo.org> (raw)
In-Reply-To: <CALCETrW78805ayUL=ZYBdFwVdDvJZus2JL0VVmEBE8=L1Nm5Sw@mail.gmail.com>
On Mon, 23 Feb 2015, Andy Lutomirski wrote:
> Is there really a need to drop privilege and then regain it or is it
> sufficient to keep the privilege permitted (and perhaps ambient, too)
> and just to have execve not drop it for you? I assume the latter.
I would think just keep the ambient set active as long as there is no
prctl switching the cap off in the child processes. Do not let it be
affected by the usual drop privs stuff.
next prev parent reply other threads:[~2015-02-23 16:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 21:56 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 [this message]
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
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=alpine.DEB.2.11.1502231046080.21888@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@ubuntu.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
all inboxes | Powered by JetHome®