X-Spam-Check-By:	sourceware.org
Message-ID:	<4696B33F.C0EAE4B8@dessent.net>
Date:	Thu, 12 Jul 2007 16:03:27 -0700
From:	Brian Dessent <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: cygrunsrv startup issues
References:	<loom DOT 20070712T125148-269 AT post DOT gmane DOT org>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

Richard wrote:

> Windows 2003 Std.
> 
> when I try to start the  cygrunsrv service, I get the following messages in the
> SSHD log.

You've got a terminology problem here.  You're trying to start the
*sshd* service, and sshd is giving you these errors.  The fact that
cygrunsrv is the generic framework used to run any Cygwin daemon as a
service does not mean this has anything to do with cygrunsrv per se. 
The errors are from sshd.

> Could not load host key: /etc/ssh_host_key
> Could not load host key: /etc/ssh_host_rsa_key
> Could not load host key: /etc/ssh_host_dsa_key
> Disabling protocol version 1. Could not load host key
> Disabling protocol version 2. Could not load host key
> sshd: no hostkeys available -- exiting.

These are indicative of incorrect permissions on those files.  Did you
run ssh-host-config?  Did you ever mess around with running sshd as a
non-service?  If yes, then that creates these files with incorrect
permissions.  In any case, delete them and re-run ssh-host-config and
they should be created with the proper owner/mode.

> I can see that the host key files are there in the cygwin/etc directory.

Existance is not sufficient.  The ssh daemon requires them to be secured
otherwise it won't start, since having them readable by untrusted users
would compromise the security of the daemon.

Brian

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

- Raw text -