All of lore.kernel.org
 help / color / mirror / Atom feed
From: daw@cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: capabilities patch (v 0.1)
Date: Wed, 10 Aug 2005 00:53:54 +0000 (UTC)	[thread overview]
Message-ID: <ddbj72$na5$1@taverner.CS.Berkeley.EDU> (raw)
In-Reply-To: 20050809214806.GA2288@clipper.ens.fr

David Madore  wrote:
>I intend to add a couple of capabilities which are normally available
>to all user processes, including capability to exec(), [...]

Once you have a mechanism that lets you prevent the untrusted program
from exec-ing a setuid/setgid program (such as your bounding set idea),
I don't see any added value in preventing the program from calling exec().

"Don't forbid what you can't prevent".  The program can always emulate
the effect of exec() in userspace (for non-setuid/setgid programs) --
doing so is tedious, but nothing prevents a malicious userspace program
from implementing such a thing, I think.

This is only a comment on forbidding exec(), not on anything else in
your proposal.

  reply	other threads:[~2005-08-10  0:54 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 [this message]
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='ddbj72$na5$1@taverner.CS.Berkeley.EDU' \
    --to=daw@cs.berkeley.edu \
    --cc=daw-usenet@taverner.CS.Berkeley.EDU \
    --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.