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: Thu, 21 Jul 2005 01:29:07 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Eli Barzilay cc: cygwin AT cygwin DOT com Subject: Re: ssh problems In-Reply-To: <17119.3923.233713.746516@tulare.cs.cornell.edu> Message-ID: References: <17099 DOT 10669 DOT 464228 DOT 125667 AT tulare DOT cs DOT cornell DOT edu> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050705221013 DOT 08cdd6b0 AT pop DOT prospeed DOT net> <17099 DOT 18679 DOT 819770 DOT 637448 AT tulare DOT cs DOT cornell DOT edu> <200507091454 DOT 38902 DOT lhall AT rfk DOT com> <17105 DOT 47620 DOT 419723 DOT 654228 AT tulare DOT cs DOT cornell DOT edu> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050710223821 DOT 03cd7140 AT 127 DOT 0 DOT 0 DOT 1> <17106 DOT 15844 DOT 889622 DOT 893399 AT tulare DOT cs DOT cornell DOT edu> <17114 DOT 65208 DOT 516047 DOT 93257 AT tulare DOT cs DOT cornell DOT edu> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050717223532 DOT 05671008 AT pop DOT prospeed DOT net> <17115 DOT 11978 DOT 668163 DOT 72702 AT tulare DOT cs DOT cornell DOT edu> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050718233351 DOT 03cd2b18 AT pop DOT prospeed DOT net> <17116 DOT 40546 DOT 768442 DOT 498799 AT tulare DOT cs DOT cornell DOT edu> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050719083147 DOT 03cdfaa8 AT pop DOT prospeed DOT net> <17117 DOT 63714 DOT 230863 DOT 91505 AT tulare DOT cs DOT cornell DOT edu> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050720225237 DOT 05748758 AT pop DOT prospeed DOT net> <17119 DOT 3923 DOT 233713 DOT 746516 AT tulare DOT cs DOT cornell DOT edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT 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/