Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 5 Aug 2002 12:39:44 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: More on SSH problems....
Message-ID:	<20020805123944.B3921@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3D4DE65D DOT 1440 DOT 6307BA AT localhost> <3D4DF0FF DOT 2181 DOT 8C91D8 AT localhost>
Mime-Version:	1.0
In-Reply-To:	<3D4DF0FF.2181.8C91D8@localhost>
User-Agent:	Mutt/1.3.22.1i

On Mon, Aug 05, 2002 at 03:29:03AM -0700, Stephen C. Biggs wrote:
> > How do you chroot after ssh login?
> 
> A shell script rather than /bin/bash is the entry 
> for the shell field in the user's passwd line.  The 
> script executes chroot to the jail with /bin/bash - 
> -login -i.  

So it's not the sshd server chroot'ing (which isn't implemented
in the official ssh sources anyway).  The problem might be related
to the fact that sshd and the shell script (another bash, that is)
is still running not chrooted (using the Cygwin DLL in /bin) and
the child bash is running using the Cygwin DLL in the chroot jail.
Are these DLLs the very same version?  This is the minimal requirement.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -