Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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:08:08 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: More on SSH problems.... Message-ID: <20020805120808.C16778@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3D4D9A65 DOT 28231 DOT 18FC4DE AT localhost> <3D4DE65D DOT 1440 DOT 6307BA AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D4DE65D.1440.6307BA@localhost> User-Agent: Mutt/1.3.22.1i On Mon, Aug 05, 2002 at 02:43:41AM -0700, Stephen C. Biggs wrote: > I do, in fact, have two copies (both the same) of > Cygwin1.dll. One is the proper one in /bin and > the other is in my chroot jail /bin since > this is the only way I can give the user the > ability to do things like 'ls', etc. > > Are you saying that this is what is killing me? Perhaps, yes. > Why doesn't it die for empty passwords? Is No idea. Coincidence? > there something in the pubkey authentication > that might be holding a reference open over the > chroot? If this is true, then chroot upon SSH > login is impossible under Cygwin! How do you chroot after ssh login? 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/