public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Chris Wright <chrisw@osdl.org>,
	David Madore <david.madore@ens.fr>,
	Linux Kernel mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: capabilities patch (v 0.1)
Date: Tue, 9 Aug 2005 15:24:41 -0700	[thread overview]
Message-ID: <20050809222441.GJ7991@shell0.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0508092259570.9779@be1.lrz>

* Bodo Eggert (7eggert@gmx.de) wrote:
> 1) I wouldn't want an exploited service to gain any privileges, even by
>    chaining userspace exploits (e.g. exec sendmail < exploitstring).  For
>    most services, I'd like CAP_EXEC being unset (but it doesn't exist).

Don't let it exec things it shouldn't.  This can be done with namespaces
or for finer-grained, that is what smth like SELinux is made for.

> 2) There are environments (linux-vserver.org) which limit root to a subset
>    of capabilities. I think they might use that feature, too. Off cause a
>    simple "suid bit" == "all capabilities" scheme won't work there.

IIRC, they effectively use the bounded set as per-context.  So it'd not
make any difference there.

thanks,
-chris

  parent reply	other threads:[~2005-08-09 22:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4zuQJ-20d-11@gated-at.bofh.it>
     [not found] ` <4zv0l-2b8-11@gated-at.bofh.it>
2005-08-09 20:21   ` capabilities patch (v 0.1) Bodo Eggert
2005-08-09 20:52     ` Chris Wright
2005-08-09 21:05       ` David Madore
2005-08-09 21:36       ` Bodo Eggert
2005-08-09 21:48         ` David Madore
2005-08-10  0:53           ` David Wagner
2005-08-09 22:24         ` Chris Wright [this message]
2005-08-09 22:58           ` Bodo Eggert
2005-08-09  5:26 David Madore
2005-08-09  5:37 ` Chris Wright
2005-08-09 20:36   ` David Madore
2005-08-09 20:28 ` Valdis.Kletnieks
2005-08-09 20:48   ` David Madore

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=20050809222441.GJ7991@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=7eggert@gmx.de \
    --cc=david.madore@ens.fr \
    --cc=linux-kernel@vger.kernel.org \
    /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