This is the mail archive of the
mailing list for the Cygwin project.
RE: Can not log in to recently enabled/configured sshd service
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 6 Feb 2008 14:55:10 -0000
- Subject: RE: Can not log in to recently enabled/configured sshd service
- References: <0100B774-FE88-4513-8AEA-6F815B97CD93@von-campe.com>
On 06 February 2008 14:41, Alfred von Campe wrote:
> debug1: Host 'gandalf' is known and matches the RSA host key.
> debug1: Found key in /home/av16209/.ssh/known_hosts:101
> debug1: ssh_rsa_verify: signature correct
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug1: SSH2_MSG_NEWKEYS received
> debug1: SSH2_MSG_SERVICE_REQUEST sent
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentications that can continue:
> debug1: Next authentication method: publickey
> debug1: Offering public key: /home/av16209/.ssh/id_rsa
> Connection closed by 126.96.36.199
> The home directory defined in the Cygwin /etc/passwd file is "//
> nasbox/av16209" which is the same home directory used on the Linux
> system that I initiated the ssh connection from (only there it's
> mounted as "/home/av16209"). I have got passwordless ssh access
> working from all my Linux systems, so that part is set up correctly.
> Any ideas as to why this is failing on the Cygwin side?
How do the perms on /home/av16209/.ssh/* look? How do they look with
sshd is very strict about not allowing logins if the key files have loose
Can't think of a witty .sigline today....
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html