mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Serge Hallyn <serge.hallyn@ubuntu.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	Andrew Lutomirski <luto@kernel.org>, "Ted Ts'o" <tytso@mit.edu>,
	Andrew Morton <akpm@linuxfoundation.org>,
	"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: Re: [RFC] capabilities: Ambient capabilities
Date: Fri, 24 Apr 2015 14:25:46 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.11.1504241424330.11285@gentwo.org> (raw)
In-Reply-To: <20150424190935.GN16377@ubuntumail>

On Fri, 24 Apr 2015, Serge Hallyn wrote:

> > I object because CAP_SETPCAP is very powerful whereas
> > CAP_NET_BIND_SERVICE, for example, isn't.  I'm fine with having a
> > switch to turn off ambient caps, but requiring the "on" state to give
>
> Would only really be needed for the initial 'enable ambient caps for this
> process tree', though.  Once that was set, add/remove'ing caps from the
> ambient set wouldn't need to be required.

Exactly. Its much simpler than alternate approaches. And its convoluted
enough.


  reply	other threads:[~2015-04-24 19:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 18:08 Andy Lutomirski
2015-03-12 21:49 ` Kees Cook
2015-03-12 22:10   ` Andrew G. Morgan
2015-03-12 22:27     ` Andrew Lutomirski
2015-03-13 13:24       ` Andrew G. Morgan
2015-03-13 16:06         ` Christoph Lameter
2015-03-13 17:58           ` Andy Lutomirski
2015-03-13 18:52             ` Christoph Lameter
2015-03-13 17:57         ` Andy Lutomirski
2015-03-13 18:52           ` Kees Cook
2015-03-13 19:03             ` Andy Lutomirski
2015-03-13 19:54               ` Kees Cook
2015-03-14 21:09           ` Andrew G. Morgan
2015-03-14 21:45             ` Andy Lutomirski
2015-03-14 22:17               ` Andrew G. Morgan
2015-03-14 22:53                 ` Andy Lutomirski
2015-03-14 22:55                 ` Andy Lutomirski
2015-03-15  0:04                   ` Andrew G. Morgan
2015-03-30 12:55                     ` Christoph Lameter
2015-03-30 14:31                       ` Andy Lutomirski
2015-03-30 15:05                         ` Christoph Lameter
2015-04-09 15:25                         ` Christoph Lameter
2015-04-23 14:01                           ` Christoph Lameter
2015-04-24 17:53                             ` Serge Hallyn
2015-04-24 18:41                               ` Andy Lutomirski
2015-04-24 19:09                                 ` Serge Hallyn
2015-04-24 19:25                                   ` Christoph Lameter [this message]
2015-04-24 19:53                                   ` Andy Lutomirski
2015-04-24 20:13                                     ` Christoph Lameter
2015-04-24 20:18                                       ` Andy Lutomirski
2015-04-24 21:15                                         ` Serge E. Hallyn
2015-04-24 22:55                                           ` Andy Lutomirski
2015-04-25  2:45                                             ` Serge Hallyn
2015-04-27 14:55                                         ` 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.1504241424330.11285@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=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=luto@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 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®