openssh 3.4p1-4. Error starting sshd service

Vince Hoffman Vince.Hoffman@uk.circle.com
Tue Jul 30 04:02:00 GMT 2002


is there anything in /var/log/sshd.log ? that what told me the permissions
on /var/empty were wrong when mine wouldnt start. (needs to be owned by
SYSTEM.SYSTEM with mode 700)

-----Original Message-----
From: Pablo Milano [mailto:pablo.milano@datatransfer.com.ar]
Sent: 29 July 2002 22:14
To: Max Bowsher; cygwin@cygwin.com
Subject: openssh 3.4p1-4. Error starting sshd service


I upgraded to openssh 3.4p1-4, and after installing it, I get the following
error when trying to start the openssh service:

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

I tried removing the service with cygrunsrv.exe -R sshd and then re-running
ssh-host-config, bit I got the same error.
I tried also uninstalling and re-installing the packages and even removing
all cygwin entries from the registry, but I couldn't succeed.
Any hints?


-----Mensaje original-----
De: Max Bowsher [mailto:maxb@ukf.net]
Enviado el: Viernes, 26 de Julio de 2002 15:42
Para: pablo.milano@datatransfer.com.ar; cygwin@cygwin.com
Asunto: Re: Openssh 3.0.2-p15: Can't validate public key when accesing
from cron


Pablo Milano wrote:
>> I am using Cygwin with openssh 3.0.2p1-5 and openssl 0.9.6c-2
>> The sshd is running in a windows 2000 server computer.
>> I use rsa keys to authenticate the users who access the ssh server
>> from linux machines (kernel 2.4.18).
>> Authentication works fine if the "ssh -i user.key user@server" is
>> run from a linux console, but it fails if the same command is run
>> from cron. The following error is returned to the standard error
>> console: "Host key verification failed."
>>
>> This happens only when trying to connect to the cygwin ssh server.
>> It works fine among linux servers.
>> Any hint?

1. Upgrade openssh - 3.0.x is: a) ancient, b) known to have security
problems.

2. The problem is likely to be that the server's host key is not in the ssh
known_hosts file for the user that cron is running ssh as. Since ssh is
running
non-interatively, it can't prompt 'Do you wat to trust this host key?'.


Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list