All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: can chroot be made safe for non-root?
Date: Mon, 21 Oct 2002 22:29:31 +0200	[thread overview]
Message-ID: <20021021202931.GA25035@lina.inka.de> (raw)
In-Reply-To: <200210201715.07150.landley@trommello.org>

On Sun, Oct 20, 2002 at 05:15:07PM -0500, Rob Landley wrote:
> Anything that wants to look at /etc/password or /etc/shadow comes to mind.  

only if it runs with elevated priveledges. If it is started under a users
chroot, the eleated privs come from suid/sgid.

Greetings
Bernd

  parent reply	other threads:[~2002-10-21 20:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16  5:51 can chroot be made safe for non-root? Eric Buddington
2002-10-16  6:44 ` Philippe Troin
2002-10-16 21:18   ` David Wagner
2002-10-16 22:04     ` Philippe Troin
2002-10-16 22:00       ` David Wagner
2002-10-19 17:44   ` Eric Buddington
2002-10-19 19:07     ` Bernd Eckenfels
     [not found]       ` <200210201715.07150.landley@trommello.org>
2002-10-21 20:29         ` Bernd Eckenfels [this message]
2002-10-22 15:42     ` Jesse Pollard
2002-10-22 16:55       ` Shaya Potter
2002-10-21 15:22   ` Alan Cox
2002-10-22  7:21     ` Ville Herva
2002-10-22 14:15       ` Shaya Potter
2002-10-22 15:55         ` Martin Josefsson
2002-10-16 21:14 ` David Wagner
2002-10-18 19:01 ` Pavel Machek
2002-10-18 20:14   ` David Wagner
2002-10-18 21:07     ` Shaya Potter
2002-10-18 21:00       ` David Wagner
2002-10-18 21:36         ` Shaya Potter
  -- strict thread matches above, loose matches on Subject: below --
2002-10-17  5:08 Niels Provos
2002-10-19 19:42 Hank Leininger
2002-10-20 10:40 ` Bernd Eckenfels
2002-10-20 14:49   ` Shaya Potter

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=20021021202931.GA25035@lina.inka.de \
    --to=ecki@lina.inka.de \
    --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.