From owner-freebsd-hackers  Fri May 30 00:05:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA03094
          for hackers-outgoing; Fri, 30 May 1997 00:05:39 -0700 (PDT)
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA03083
          for <hackers@FreeBSD.ORG>; Fri, 30 May 1997 00:05:34 -0700 (PDT)
Received: from gid.co.uk (uucp@localhost)
          by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP
	  id HAA28052; Fri, 30 May 1997 07:58:55 +0100 (BST)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Fri, 30 May 1997 07:51:30 +0100
X-Sender: rb@194.32.164.1
Message-Id: <l03020900afb428738dc8@[194.32.164.2]>
In-Reply-To: <Pine.BSF.3.91.970530090251.14689q-100000@panda.hilink.com.au>
References: <l03020900afb38f29f0df@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 30 May 1997 07:48:27 +0100
To: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
From: Bob Bishop <rb@gid.co.uk>
Subject: Re: Correct way to chroot for shell account users?
Cc: hackers@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

At 0:03 +0100 30/5/97, Daniel O'Callaghan wrote:
>On Thu, 29 May 1997, Bob Bishop wrote:
>
>> I'm sure I'm being desperately naive here, but isn't it sufficient for
>> safety to make chroot(2) a successful no-op unless / is really / (ie the
>> process isn't chrooted already)?
>
>That means that you can't run anon ftp properly in a chrooted file system,
>because ftpd is not allowed to chroot again.

Why would you want to do that?


--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK