Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Message-Id: <6.2.1.2.0.20050721014238.057a59c8@pop.prospeed.net>
Date: Thu, 21 Jul 2005 01:53:37 -0400
To: cygwin AT cygwin DOT com, Eli Barzilay <eli AT barzilay DOT org>
From: Larry Hall <lhall AT prospeed DOT net>
Subject: Re: ssh problems
Cc: cygwin AT cygwin DOT com
In-Reply-To: <Pine.GSO.4.61.0507210009150.22383@slinky.cs.nyu.edu>
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>  <Pine DOT GSO DOT 4 DOT 61 DOT 0507110927320 DOT 6749 AT slinky DOT cs DOT nyu DOT edu>  <Pine DOT GSO DOT 4 DOT 61 DOT 0507102317520 DOT 9496 AT slinky DOT cs DOT nyu 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>  <Pine DOT GSO DOT 4 DOT 61 DOT 0507210009150 DOT 22383 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:29 AM 7/21/2005, you wrote:
>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").


That's going back to where we started actually.  His original problem 
was that ssh was bombing out on him when he was running it as part of
his build environment with pubkey authentication.  Password authentication
worked.  The theory was that the build environment needed a
Windows authenticated user, which is why we started down the path of 
running sshd as a service under his ID.  For some reason, he's finding
he cannot start sshd using his ID with cygrunsrv.  See the thread for
details.  But essentially he's at the point here that would be synonymous
with being able to a run typical installation of sshd from the SYSTEM-owned 
shell but not from cygrunsrv.  So if that sparks any ideas from you, I'm 
sure Eli would like to hear them. :-)


>> > 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"?


Well, a variant.  I told him to chown this to be his ID.  But maybe it
makes sense to just loosen the perms on all the affected files.  At this
point, it can't hurt. ;-)


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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