From: Aaron Jones <aaronmdjones@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>, Christoph Lameter <cl@linux.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
"Ted Ts'o" <tytso@mit.edu>,
"Andrew G. Morgan" <morgan@kernel.org>,
Andrew Morton <akpm@linuxfoundation.org>,
Serge Hallyn <serge.hallyn@ubuntu.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Linux API <linux-api@vger.kernel.org>,
Austin S Hemmelgarn <ahferroin7@gmail.com>,
linux-security-module <linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Serge Hallyn <serge.hallyn@canonical.com>,
Markku Savela <msa@moth.iki.fi>,
Kees Cook <keescook@chromium.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2 1/2] capabilities: Ambient capabilities
Date: Tue, 19 May 2015 20:22:17 +0000 [thread overview]
Message-ID: <555B9B79.9080806@gmail.com> (raw)
In-Reply-To: <CALCETrW6DndOnC5ego+R5rwjoXeFo04cSO4Z2qZnhiJpEPBE=Q@mail.gmail.com>
On 19/05/15 20:07, Andy Lutomirski wrote:> It's in the cover letter,
rather vaguely. I think I want to change
> the setpriv syntax a bit before sending it upstream, though -- it's
> sucks that you have to duplicate the option.
>
> Perhaps the ambient-caps option should implicitly raise inheritable
> caps if they're not already raised. Or maybe the absence of an
> inh-caps rule should cause any requested ambient caps to be made
> inheritable as well.
>
> --Andy
I propose an additional --ambient-inh option to copy everything from
--inh-caps to the ambient set. Explicit is better than implicit.
--
Aaron Jones
next prev parent reply other threads:[~2015-05-19 20:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 6:39 [PATCH v2 0/2] capabilities: Ambient capabilities Andy Lutomirski
2015-05-15 6:39 ` [PATCH v2 1/2] " Andy Lutomirski
2015-05-15 11:32 ` Lukasz Pawelczyk
2015-05-15 12:03 ` Andy Lutomirski
2015-05-15 14:19 ` Christoph Lameter
2015-05-18 19:48 ` Andy Lutomirski
2015-05-19 15:37 ` Christoph Lameter
2015-05-19 17:20 ` Andy Lutomirski
2015-05-19 20:03 ` Christoph Lameter
2015-05-19 20:07 ` Andy Lutomirski
2015-05-19 20:22 ` Aaron Jones [this message]
2015-05-19 20:23 ` Andy Lutomirski
2015-05-15 14:31 ` Christoph Lameter
2015-05-18 19:43 ` Andy Lutomirski
2015-05-27 22:35 ` Andy Lutomirski
2015-05-23 19:37 ` Serge Hallyn
2015-05-26 16:23 ` Christoph Lameter
2015-05-27 22:44 ` Andy Lutomirski
2015-05-15 6:39 ` [PATCH v2 2/2] capabilities: Add a securebit to disable PR_CAP_AMBIENT_RAISE Andy Lutomirski
2015-05-23 19:45 ` Serge E. Hallyn
2015-05-24 20:39 ` Andrew G. Morgan
2015-05-20 19:47 ` [PATCH v2 0/2] capabilities: Ambient capabilities Andy Lutomirski
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=555B9B79.9080806@gmail.com \
--to=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=keescook@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).