"umesh" <umesh.gamare@gmail.com> writes:
> Hi,
> Here is what i have done so far,
>
> 'ssh-keygen -t dsa' on host 1
>
>
> copied over the "id_dsa.pub" as "authorized_keys" at host2
>
>
> trying to login using ssh/sftp from host1 to host2 without password,
> but the remote host2 asks for the password.
> Foll. is the log generated : (apparantly there is nothing relevant that
>
> tells why it has failed!)
>
> ================================================
> Connecting to host2...
> OpenSSH_3.9p1, OpenSSL 0.9.7d 17 Mar 2004
> debug1: Connecting to hos2 [123.45.67.89] port 22.
> debug1: Connection established.
> debug1: identity file $home/.ssh/id_rsa type -1
> debug1: identity file $home/.ssh/id_dsa type 2
> debug1: Remote protocol version 2.0, remote software version
> OpenSSH_3.9p1
> debug1: match: OpenSSH_3.9p1 pat OpenSSH*
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_3.9p1
> 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 'drpriskweb03' is known and matches the RSA host key.
> debug1: Found key in $home/.ssh/known_hosts:1
> 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,password,keyboard-interacti
> debug1: Next authentication method: publickey
> debug1: Trying private key: $home/.ssh/id_rsa
> debug1: Offering public key: $home/.ssh/id_dsa

Dunno if this is normal or not, but the two lines above are handy.

What you haven't posted is what sshd on the remote server is pushing
to its logs. That'll probably give you more clues. Perhaps the
remote server isn't configured to accept publickey(?), or you have
borked the file permissions on the key files. SSH won't use em if
the file permissions aren't right. I think you'll find details in
the man pages.


--
Todd H.
http://www.toddh.net/