This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: sshd service will not start on Windows 7
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 19 Apr 2013 10:53:50 -0400
- Subject: Re: sshd service will not start on Windows 7
- References: <1359486853591-95750 dot post at n5 dot nabble dot com> <51082B30 dot 3020303 at prager dot ws> <51082C6E dot 5020409 at gmail dot com> <1359549388 dot 9218 dot YahooMailNeo at web162704 dot mail dot bf1 dot yahoo dot com> <CAPUpn4j=AkJovtKvwcPwcdEruYUAENvsLiQZaYwaxu+2Mo-2UQ at mail dot gmail dot com> <5109E15C dot 20204 at cygwin dot com> <loom dot 20130321T113217-113 at post dot gmane dot org> <1366332088377-97938 dot post at n5 dot nabble dot com>
- Reply-to: cygwin at cygwin dot com
On 4/18/2013 8:41 PM, b45710n wrote:
Jamie Stallwood wrote
I found, by enabling shell logon for cyg_server and then running sshd,
that
/etc/ssh*_key permissions were too lax.
use the command: chmod g-rwx /etc/ssh*_key to fix these permissions.
What does that command do?
It removes the group read, write, and execute permissions for the SSH
keys in /etc. See 'man chmod' for more. There's no need to try to undo
this change though. It's appropriate that these files not allow group
access to these files.
Possibly relevant:
The message I get is:
$ net start sshd
The CYGWIN sshd service is starting.
The CYGWIN sshd service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
$ NET HELPMSG 3534
The service did not report an error.
I followed the instructions at
http://www.scottmurphy.info/open-ssh-server-sshd-cygwin-windows
<http://www.scottmurphy.info/open-ssh-server-sshd-cygwin-windows> to set
up sshd on windows via cygin.
Generally, this list frowns on the practice of consulting alternate
resources on the web for configuration help and then coming back to
the Cygwin site/list when problems arise as a result. Practically, we
can't control all the sites out there that may have some configuration
information for SSH and other Cygwin packages. So we ask that you
follow-up with the original providers if the procedures, information,
and advice that they provide don't work for you.
OK, with formalities out of the way, let's talk a bit more about your
problem. First, a quick perusal of the instructions your followed doesn't
raise any obvious red flags, other than the general notation that the
instructions are dated ("ntsec" and "tty" are obsolete settings for
the CYGWIN environment variable and are now ignored). So we need to
see more information from you about your current configuration and what
else you've tried to address this issue. To that end, please read and
follow the problem reporting guidelines found at the link below for any
follow-up you may have to this list.
> Problem reports: http://cygwin.com/problems.html
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple