Problem getting beyond first machine with ssh and ssh-agent

From: James Moore (banshee_at_banshee.com)
Date: 11/18/04


Date: Thu, 18 Nov 2004 11:48:36 -0800

Setup: one cygwin box, one Fedora FC2 box, one Redhat 7.3 box. Starting
from cygwin, I can use ssh-agent to log in to either Linux box without being
asked for a password. I assume this means I've correctly copied around the
authorized_keys and that permissions are correct.

The problem is that I'm asked for the password when ssh-ing the second time;
ssh machine1 doesn't ask for a password, but an ssh from machine1 to
machine1 (between the two linux boxes) does ask for a password.

Suggestions?

>From the cygwin box to the first linux box I get:

bash-2.05b$ ssh -v james@server2
OpenSSH_3.9p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading configuration data /home/JamesMoore/.ssh/config
debug1: Connecting to server2.banshee.com [216.162.215.49] port 22.
debug1: Connection established.
debug1: identity file /home/JamesMoore/.ssh/identity type -1
debug1: identity file /home/JamesMoore/.ssh/id_rsa type -1
debug1: identity file /home/JamesMoore/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, 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 'server2.banshee.com' is known and matches the RSA host key.
debug1: Found key in /home/JamesMoore/.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-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /home/JamesMoore/.ssh/id_dsa
debug1: Server accepts key: pkalg ssh-dss blen 433
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Requesting X11 forwarding with authentication spoofing.

>From that linux box to the other linux box I get:

[james@server2 james]$ ssh -v server1
OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: restore_uid
debug1: ssh_connect: getuid 500 geteuid 0 anon 1
debug1: Connecting to server1 [216.162.215.217] port 22.
debug1: temporarily_use_uid: 500/503 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 500/503 (e=0)
debug1: restore_uid
debug1: Connection established.
debug1: read PEM private key done: type DSA
debug1: read PEM private key done: type RSA
debug1: identity file /home/james/.ssh/identity type -1
debug1: identity file /home/james/.ssh/id_rsa type -1
debug1: identity file /home/james/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH*
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.1p1
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 sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 139/256
debug1: bits set: 972/2048
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'server1' is known and matches the RSA host key.
debug1: Found key in /home/james/.ssh/known_hosts:1
debug1: bits set: 989/2048
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try privkey: /home/james/.ssh/identity
debug1: try privkey: /home/james/.ssh/id_rsa
debug1: try pubkey: /home/james/.ssh/id_dsa
debug1: input_userauth_pk_ok: pkalg ssh-dss blen 434 lastkey 0x8086e10 hint
2
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
Enter passphrase for key '/home/james/.ssh/id_dsa':

 - James
      banshee@banshee.com



Relevant Pages

  • Re: SSH from windows to linux using public key authentication
    ... Linux Linux wrote: ... public key authentication. ... I have copied exact same public key to my Prolinux and it's not working. ... debug1: Next authentication method: publickey ...
    (RedHat)
  • Re: OpenSSH_3.1p1 auth problems
    ... but you are using protocol 2. ... .ssh/to the remote machine. ... debug1: next auth method to try is publickey ... debug1: read PEM private key done: type DSA ...
    (comp.os.linux.security)
  • Re: OpenSSH_3.1p1 auth problems
    ... but you are using protocol 2. ... .ssh/to the remote machine. ... debug1: next auth method to try is publickey ... debug1: read PEM private key done: type DSA ...
    (comp.security.ssh)
  • Re: ssh client problem
    ... authentication method he does not want to use. ... >debug1: Connection established. ... >debug2: we did not send a packet, ... we sent a password packet, ...
    (comp.os.linux.misc)
  • Re: pubkey authentication problem
    ... The RSA client key generated by F-Secure ... But the key still doesn't work for authentication. ... debug1: done: KEX2. ... userauth-request for user schmidt service ssh-connection ...
    (comp.security.ssh)