From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3554 invoked by alias); 21 Jul 2005 05:30:01 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 3513 invoked by uid 22791); 21 Jul 2005 05:29:57 -0000 Received: from slinky.cs.nyu.edu (HELO slinky.cs.nyu.edu) (128.122.20.14) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 21 Jul 2005 05:29:57 +0000 Received: from localhost (localhost [127.0.0.1]) by slinky.cs.nyu.edu (8.12.10+Sun/8.12.10) with ESMTP id j6L5T7uA022806; Thu, 21 Jul 2005 01:29:11 -0400 (EDT) Date: Thu, 21 Jul 2005 05:53:00 -0000 From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: Eli Barzilay cc: cygwin@cygwin.com Subject: Re: ssh problems In-Reply-To: <17119.3923.233713.746516@tulare.cs.cornell.edu> Message-ID: References: <17099.10669.464228.125667@tulare.cs.cornell.edu> <6.2.1.2.0.20050705221013.08cdd6b0@pop.prospeed.net> <17099.18679.819770.637448@tulare.cs.cornell.edu> <200507091454.38902.lhall@rfk.com> <17105.47620.419723.654228@tulare.cs.cornell.edu> <6.2.1.2.0.20050710223821.03cd7140@127.0.0.1> <17106.15844.889622.893399@tulare.cs.cornell.edu> <17114.65208.516047.93257@tulare.cs.cornell.edu> <6.2.1.2.0.20050717223532.05671008@pop.prospeed.net> <17115.11978.668163.72702@tulare.cs.cornell.edu> <6.2.1.2.0.20050718233351.03cd2b18@pop.prospeed.net> <17116.40546.768442.498799@tulare.cs.cornell.edu> <6.2.1.2.0.20050719083147.03cdfaa8@pop.prospeed.net> <17117.63714.230863.91505@tulare.cs.cornell.edu> <6.2.1.2.0.20050720225237.05748758@pop.prospeed.net> <17119.3923.233713.746516@tulare.cs.cornell.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2005-07/txt/msg00959.txt.bz2 On Wed, 20 Jul 2005, Eli Barzilay wrote: > On Jul 20, Larry Hall wrote: > > At 03:10 AM 7/20/2005, you wrote: > > > > > >It did run into permission problems -- the /etc/ssh* keys were not > > >readable. Looks like chowning them didn't help at all. Finally, I > > >resorted to removeing them and re-runnning ssh-host-config to > > >regenerate. Now running sshd directly works, but trying it through > > >cygrunsrv still has the same problem... > > > > Hm, this may be getting to the time where you need to try strace or > > build a debug version of cygrunsrv and run gdb on it. > > I didn't think of stracing cygrunsrv... Building a debug version > sounds like yet more work in an area I don't have much experience > with. Try running sshd from a SYSTEM-owned shell (Google for "cygwin system-owned shell"). > > I'm not sure what's holding you back now... > > Mainly the fact that I'm fine with starting my own sshd, even if its > manual. (I'll try a quick strace.) I don't recall the whole thread, but have you tried "chmod 666 /var/log/sshd.log"? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/