This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: OpenSSH_3.9p1 and Could not load host key


At 04:16 PM 3/28/2005, you wrote:
>I have included cygcheck.out.
>
>The OpenSSH_3.9 which I used from an OpenBSD 3.6 system. 
>I have a lot less control over, thought I would have thought that
>a new version of sshd on my Windows XP should be a able to speak 
>to an older ssh on a differing machine.


OK, it wasn't clear to me that you were sshing into your Windows box from 
some other platform.  That's fine.  From your cygcheck output I can see 
you're running everything current in Cygwin, which is the first step.  But 
now rereading your original post you say:

>Invoked from bash we get:
>
>/usr/sbin/sshd -D -d -d -d
>debug2: load_server_config: filename /etc/sshd_config
>debug2: load_server_config: done config len = 205
>debug2: parse_server_config: config /etc/sshd_config len 205
>debug1: sshd version OpenSSH_3.9p1
>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.


If you're not doing this from a bash that's run as 'SYSTEM', then that's 
your problem.  You'll need to install a duplicate service to the one you
already have and give it these debug flags.  Then you can stop the current
service and start this new one.  Alternatively, you could temporarily modify
your original install but this is more error prone.  Otherwise, if you simply
*have* to start the debug server from a console, see:

<http://cygwin.com/ml/cygwin/2004-08/msg01132.html>

This will tell you one way of getting a 'SYSTEM' owned shell that you can 
use.  


>I also found some more information. using ssh to my Windows XP works
>fine if that machine does not have an id_rsa.pub entry in my
>.ssh/authorized_keys.


You mean it works if you don't run the server in debug mode and you enter
your Windows password, right?  That would imply a key mismatch between 
client and server.  Get your debug server set up properly (as above) and 
run through the scenario again with the RSA key.  The debug output should 
point you at the problem there.




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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]