From owner-freebsd-hackers  Sun May 25 18:00:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA19286
          for hackers-outgoing; Sun, 25 May 1997 18:00:22 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA19280
          for <hackers@FreeBSD.ORG>; Sun, 25 May 1997 18:00:17 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id RAA09343;
	Sun, 25 May 1997 17:55:21 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd009341; Mon May 26 00:55:12 1997
Date: Sun, 25 May 1997 17:54:35 -0700 (PDT)
From: Julian Elischer <julian@current1.whistle.com>
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: hackers@FreeBSD.ORG
Subject: Re: Correct way to chroot for shell account users?
In-Reply-To: <Pine.NEB.3.95.970525144745.28807A-100000@mail.cdsnet.net>
Message-ID: <Pine.BSF.3.95.970525175206.11253A-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



There are several people including myself who have hacked login to chroot
before running the shell

I even had a version that re-red the passwd file in the new chroot
environ and re-read the parameters from there. It turns out to be a very
simple hack.
I can't give code at the moment though..I think I lost it..

julian

On Sun, 25 May 1997, Jaye Mathisen wrote:

> 
> 
> Anybody got any tips on how to write  a secure shell to exec on login to
> set a users environment to the "right thing".
> 
> (I don't mean a rsh type secure shell, but rather a good secure thing
> to have in /etc/master.passwd that execs the real shell in a chroot'd 
> environment.).
> 
> Any code appreciated as well.  Thanks.
> 
> 
> 
>