Yeah, start with client side debugging and see if it tells you anything.
You can tell the version like this:
ssh -V
It should be something like:
OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
Here's an example of a correct DSA pub key handling from my debug out put:
$ ssh -v [EMAIL PROTECTED]
OpenSSH_4.5p1, OpenSSL 0.9.8d 28 Sep 2006
debug1: Connecting to inversoft.com [72.36.133.78] port 22.
debug1: Connection established.
debug1: identity file /home/bpontarelli/.ssh/identity type -1
debug1: identity file /home/bpontarelli/.ssh/id_rsa type 1
debug1: identity file /home/bpontarelli/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version
OpenSSH_4.3p2 Debian-5ubuntu1
debug1: match: OpenSSH_4.3p2 Debian-5ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.5
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 'inversoft.com' is known and matches the RSA host key.
debug1: Found key in /home/bpontarelli/.ssh/known_hosts:21
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
debug1: Next authentication method: publickey
debug1: Trying private key: /home/bpontarelli/.ssh/identity
debug1: Offering public key: /home/bpontarelli/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Offering public key: /home/bpontarelli/.ssh/id_dsa
debug1: Server accepts key: pkalg ssh-dss blen 817
debug1: read PEM private key done: type DSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
Feel free to send back your debug log if you need help decoding it.
Also, it could be on the server side, but you would need root on the
server to look into the log files there, which you might not have. Let's
see how far the client side debugging gets us.
-bp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
