Keeps asking password after putting the id_rsa.pub in ~/.ssh/authorized_keys on remote host

[Larry Hall (Cygwin)]

Tzung-Cheng Yang wrote:
> Hi,
> 
> I tried to make password_less sftp work.
> 
> After I putting the id_rsa.pub in ~/.ssh/authorized_keys on remote host, 
> the sftp still keeps
> asking password.
> 
> I also changed the following on the /etc/ssh/sshd_config file on remote 
> hosts
> 
> RSAAuthentication yes
> PubkeyAuthentication yes
> AuthorizedKeysFile      .ssh/authorized_keys
> 
> Anything to do to solve the problem?
> 
> Here is the message
> 
> $ sftp -v tcy@nhic2
> Connecting to nhic2...
> OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006
> debug1: Connecting to nhic2 [140.90.22.252] port 22.
> debug1: Connection established.
> debug1: identity file /cygdrive/h/.ssh/id_rsa type 1
> debug1: identity file /cygdrive/h/.ssh/id_dsa type -1
> debug1: Remote protocol version 2.0, remote software version OpenSSH_3.9p1
> debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.*
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_4.3
> debug1: SSH2_MSG_KEXINIT sent
> debug1: SSH2_MSG_KEXINIT received
> debug1: kex: server->client aes128-cbc hmac-md5 none
> debug1: kex: client->server aes128-cbc hmac-md5 none
> debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
> debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
> debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
> debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
> debug1: Host 'nhic2' is known and matches the RSA host key.
> debug1: Found key in /cygdrive/h/.ssh/known_hosts:2
> 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: 
> publickey,gssapi-with-mic,password
> debug1: Next authentication method: publickey
> debug1: Offering public key: /cygdrive/h/.ssh/id_rsa


Please read and follow the problem reporting guidelines outlined
here:

> Problem reports:       http://cygwin.com/problems.html

Pay close attention to the portion of the guidelines that recommends
*attaching* (not appending) your cygcheck output.  Without this
information, it's quite difficult to eliminate some of the common
issues from the decision tree.  My WAG is that /cygdrive/h is a
network share.  If that's the case, you need to look at:

smbntsec in <http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>

and

<http://cygwin.com/faq/faq-nochunks.html#faq.using.shares>

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (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/