Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.2.1.2.0.20050328174310.03864658@pop.prospeed.net> Date: Mon, 28 Mar 2005 18:07:12 -0500 To: "Peter Fraser" , "Cygwin List" From: Larry Hall Subject: RE: OpenSSH_3.9p1 and Could not load host key In-Reply-To: <887691AAF56A5C4A803F6850D35C089D3A7AD0@cerveau.thoughts.th inkage.ca> References: <887691AAF56A5C4A803F6850D35C089D3A7AD0 AT cerveau DOT thoughts DOT thinkage DOT ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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: 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/