From: Larry Hall <lh-no-personal-replies-please@cygwin.com>
To: Eli Barzilay <eli@barzilay.org>, Cygwin List <cygwin@cygwin.com>
Subject: Re: ssh problems
Date: Tue, 19 Jul 2005 12:40:00 -0000 [thread overview]
Message-ID: <6.2.1.2.0.20050719083147.03cdfaa8@pop.prospeed.net> (raw)
In-Reply-To: <17116.40546.768442.498799@tulare.cs.cornell.edu>
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/
next prev parent reply other threads:[~2005-07-19 12:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 0:45 Eli Barzilay
2005-07-06 2:15 ` Larry Hall
2005-07-06 2:59 ` Eli Barzilay
2005-07-06 9:29 ` Dave Korn
2005-07-09 18:55 ` Larry Hall
2005-07-11 0:15 ` Eli Barzilay
2005-07-11 3:08 ` Larry Hall
2005-07-11 9:37 ` Eli Barzilay
2005-07-11 13:31 ` Igor Pechtchanski
2005-07-11 3:35 ` Igor Pechtchanski
2005-07-18 0:58 ` Eli Barzilay
2005-07-18 3:05 ` Larry Hall
2005-07-18 4:23 ` Eli Barzilay
2005-07-19 3:43 ` Larry Hall
2005-07-19 6:32 ` Eli Barzilay
2005-07-19 12:40 ` Larry Hall [this message]
2005-07-20 7:10 ` Eli Barzilay
2005-07-21 2:59 ` Larry Hall
2005-07-21 3:27 ` Eli Barzilay
2005-07-21 3:38 ` Larry Hall
2005-07-21 5:53 ` Igor Pechtchanski
2005-07-21 5:57 ` Larry Hall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6.2.1.2.0.20050719083147.03cdfaa8@pop.prospeed.net \
--to=lh-no-personal-replies-please@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=eli@barzilay.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).