From: Shaya Potter <spotter@cs.columbia.edu>
To: Bernd Eckenfels <ecki-news2002-09@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can chroot be made safe for non-root?
Date: 20 Oct 2002 10:49:14 -0400 [thread overview]
Message-ID: <1035125354.2172.5.camel@zaphod> (raw)
In-Reply-To: <E183DV6-0004ha-00@sites.inka.de>
On Sun, 2002-10-20 at 06:40, Bernd Eckenfels wrote:
> In article <200210191942.g9JJg2U26376@marc2.theaimsgroup.com> you wrote:
> > IIRC, FreeBSD allow a chroot'ed process to chroot again if and only if
> > the
> > new root is a subdirectory of the initial chroot. This allows things
> > like
> > traditional, chrooting anonymous FTP to be run under an initial chroot.
>
> well, you can only changeroot in a subdir anyway, so this is not the point
> that freebsd is allowing a chroot in a chroot. As far as I know they simply
> solved the break out issue.
didn't see the mail this is in response to, but are you talking about
FreeBSD's jail() syscall? or are you talking about chroot() actually
being able to nest?
next prev parent reply other threads:[~2002-10-20 14:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 19:42 can chroot be made safe for non-root? Hank Leininger
2002-10-20 10:40 ` Bernd Eckenfels
2002-10-20 14:49 ` Shaya Potter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 5:08 Niels Provos
2002-10-16 5:51 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
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
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=1035125354.2172.5.camel@zaphod \
--to=spotter@cs.columbia.edu \
--cc=ecki-news2002-09@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox