From: Andy Lutomirski <luto@kernel.org>
To: Serge Hallyn <serge.hallyn@ubuntu.com>,
Andrew Morton <akpm@linuxfoundation.org>,
James Morris <james.l.morris@oracle.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Andrew Lutomirski <luto@kernel.org>, Ted Ts'o <tytso@mit.edu>,
"Andrew G. Morgan" <morgan@kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Austin S Hemmelgarn <ahferroin7@gmail.com>,
linux-security-module <linux-security-module@vger.kernel.org>,
Aaron Jones <aaronmdjones@gmail.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
LKML <linux-kernel@vger.kernel.org>,
Markku Savela <msa@moth.iki.fi>,
Kees Cook <keescook@chromium.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH v3 0/2] capabilities: Ambient capability patchset
Date: Wed, 27 May 2015 16:47:57 -0700 [thread overview]
Message-ID: <cover.1432770087.git.luto@kernel.org> (raw)
This adds ambient capabilities. See the individual patch changelogs
for details.
Preliminary userspace code is here:
https://git.kernel.org/cgit/linux/kernel/git/luto/util-linux-playground.git/commit/?h=cap_ambient&id=7f5afbd175d2
James or akpm, I think this is ready for 4.2. Can one of you queue it up?
Thanks,
Andy
Changes from v2:
- Improve the patch 1 changelog a bit.
- Add acks.
- Add comment clarifying the pE' rule.
- s/except/expect
Changes from v1:
- Lots of cleanups to the ambient cap code.
- The securebit is new.
Andy Lutomirski (2):
capabilities: Ambient capabilities
capabilities: Add a securebit to disable PR_CAP_AMBIENT_RAISE
fs/proc/array.c | 5 ++-
include/linux/cred.h | 8 ++++
include/uapi/linux/prctl.h | 6 +++
include/uapi/linux/securebits.h | 11 ++++-
kernel/user_namespace.c | 1 +
security/commoncap.c | 92 ++++++++++++++++++++++++++++++++++++-----
security/keys/process_keys.c | 1 +
7 files changed, 112 insertions(+), 12 deletions(-)
--
2.1.0
next reply other threads:[~2015-05-27 23:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 23:47 Andy Lutomirski [this message]
[not found] ` <cover.1432770087.git.luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-05-27 23:47 ` [PATCH v3 1/2] capabilities: Ambient capabilities Andy Lutomirski
2015-05-27 23:47 ` Andy Lutomirski
2015-06-09 23:09 ` Kees Cook
[not found] ` <CAGXu5j+Y85U9pjZUO0LM8rOO-YJrqvwzsXNjmaxN=D+JiQrpJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-10 0:00 ` Andy Lutomirski
2015-06-10 0:00 ` Andy Lutomirski
[not found] ` <CALCETrXz9e_PiAZaGRLuunyDu3-nRW_jopvvXcQwU3gN=sm_SA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-10 19:24 ` Kees Cook
2015-06-10 19:24 ` Kees Cook
2015-06-04 19:33 ` [PATCH v3 0/2] capabilities: Ambient capability patchset Andy Lutomirski
2015-06-04 19:33 ` Andy Lutomirski
2015-05-27 23:47 ` [PATCH v3 2/2] capabilities: Add a securebit to disable PR_CAP_AMBIENT_RAISE Andy Lutomirski
2015-06-04 22:03 ` Serge E. Hallyn
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=cover.1432770087.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=aaronmdjones@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=akpm@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=james.l.morris@oracle.com \
--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=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 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.