From: David Madore <david.madore@ens.fr>
To: Linux Kernel mailing-list <linux-kernel@vger.kernel.org>
Cc: 7eggert@gmx.de, Chris Wright <chrisw@osdl.org>
Subject: Re: capabilities patch (v 0.1)
Date: Tue, 9 Aug 2005 23:05:05 +0200 [thread overview]
Message-ID: <20050809210505.GA16404@clipper.ens.fr> (raw)
In-Reply-To: <20050809205206.GW7762@shell0.pdx.osdl.net>
On Tue, Aug 09, 2005 at 01:52:06PM -0700, Chris Wright wrote:
> * Bodo Eggert (harvested.in.lkml@7eggert.dyndns.org) wrote:
> > 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.
suid exec _must_ reset to full caps or we have the sendmail disaster
again. However, that is _if_ execve() succeeds. It is quite possible
that execve() should fail, and that is precisely what my patch does:
if a process has bounded capabilities, it _may not_ exec suid.
--
David A. Madore
(david.madore@ens.fr,
http://www.madore.org/~david/ )
next prev parent reply other threads:[~2005-08-09 21:05 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 [this message]
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=20050809210505.GA16404@clipper.ens.fr \
--to=david.madore@ens.fr \
--cc=7eggert@gmx.de \
--cc=chrisw@osdl.org \
--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