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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.2.1.2.0.20050719083147.03cdfaa8@pop.prospeed.net>
Date: Tue, 19 Jul 2005 08:39:27 -0400
To: Eli Barzilay <eli AT barzilay DOT org>, Cygwin List <cygwin AT cygwin DOT com>
From: Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject: Re: ssh problems
In-Reply-To: <17116.40546.768442.498799@tulare.cs.cornell.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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 02:32 AM 7/19/2005, you wrote:
>I did the additional chown, and my username is a mamber of the
>administrators group, but I'm still getting the same error (1053).  Is
>there any log file or something that will hint at the problem?  


Only /var/log/sshd.log but this really only provides information if
sshd is running.  Worth a check though.


>The
>event viewer is not helping --
>
>  The description for Event ID ( 0 ) in Source ( sshd ) cannot be
>  found. The local computer may not have the necessary registry
>  information or message DLL files to display messages from a remote
>  computer. You may be able to use the /AUXSOURCE= flag to retrieve
>  this description; see Help and Support for details. The following
>  information is part of the event: sshd : PID 812 : starting service
>  `sshd' failed: execv: 1, Operation not permitted.


So it appears there's still a permission problem.  Try running sshd
directly yourself now.  You can also run it under strace to see if 
the output points at something interesting (please don't sent the 
entire output of strace to the list though - only send a piece if 
you believe there's something interesting or relevant - if you're
not pretty sure, don't bother).  

As a last resort, you can try adding the other permissions listed in 
'/usr/share/doc/Cygwin/openssh.README' to your user name and see if 
this helps.  I actually did this first and then backed off these 
permissions once I got it working until I found the minimal set I 
needed but maybe Windows wasn't giving up some privileges I gave,
or at least not without a reboot (which I didn't do).


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