From: Chris Wright <chrisw@osdl.org>
To: 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 13:52:06 -0700 [thread overview]
Message-ID: <20050809205206.GW7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <E1E2aaq-0002WB-Tj@be1.lrz>
* Bodo Eggert (harvested.in.lkml@7eggert.dyndns.org) wrote:
> Chris Wright <chrisw@osdl.org> wrote:
> > * David Madore (david.madore@ens.fr) wrote:
>
> >> * Second, a much more extensive change, the patch introduces a third
> >> set of capabilities for every process, the "bounding" set. Normally
> >
> > this is not a good idea. don't add more sets. if you really want to
> > work on this i'll give you all the patches that have been done thus far,
> > plus a set of tests that look at all the execve, ptrace, setuid type of
> > corner cases.
>
> How are you going to tell processes that may exec suid (or set-capability-)
> programs from those that aren't supposed to gain certain capabilities?
typically you'd expect exec suid will reset to full caps.
next prev parent reply other threads:[~2005-08-09 20:52 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 [this message]
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
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=20050809205206.GW7762@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 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.