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
From: "Stephen C. Biggs" <yyyyy50 AT hotpop DOT com>
To: cygwin AT cygwin DOT com
Date: Mon, 05 Aug 2002 03:50:21 -0700
MIME-Version: 1.0
Subject: Re: More on SSH problems....
Message-ID: <3D4DF5FD.14250.A012E2@localhost>
In-reply-to: <20020805123944.B3921@cygbert.vinschen.de>
References: <3D4DF0FF DOT 2181 DOT 8C91D8 AT localhost>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

On 5 Aug 2002 at 12:39, Corinna Vinschen 
wrote:

> 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.

This sounds about right because it doesn't 
dump the connection until after it logs on.  But, 
it is the sshd server that dumps the connection, 
not ssh. (In the client side: "Connection to 
localhost closed by remote host").  This is now 
getting me very confused!  Unless something is 
being transmitted wrong, but it only seems to 
matter when public key authentication is being 
used.  Perhaps something needs the dll 
constantly in the client?  Bad news!

> Are these DLLs the very same version?  This is the minimal requirement.
> 

Yes. I did an explicit copy as part of my setting 
up of the chroot jail, and made sure that they 
were sync'd up after I tried to upgrade (see the 
"Oops?" thread).


--
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/