SSH Public/Private Key Fail. Help Please!

hawk__0 · 11-06-2008, 06:04 PM

When I try and set up pub/priv key authentication I am still asked to put in a password. Here is output of ssh -vvv. I copied a known working authorized_keys file with the servers public key in it to my desktop. The server is unable to connect without typing in a password. Why is this happening?

Code:

OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.12.90 [192.168.12.90] port 22.
debug1: Connection established.
debug1: identity file /u1/dcpa/work/.ssh/identity type -1
debug1: identity file /u1/dcpa/work/.ssh/id_rsa type -1
debug3: Not a RSA1 key file /u1/dcpa/work/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /u1/dcpa/work/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-3ubuntu1
debug1: match: OpenSSH_5.1p1 Debian-3ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.6
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
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
debug2: dh_gen_key: priv key bits set: 120/256
debug2: bits set: 510/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /u1/dcpa/work/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug1: Host '192.168.12.90' is known and matches the RSA host key.
debug1: Found key in /u1/dcpa/work/.ssh/known_hosts:1
debug2: bits set: 525/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /u1/dcpa/work/.ssh/identity (0)
debug2: key: /u1/dcpa/work/.ssh/id_rsa (0)
debug2: key: /u1/dcpa/work/.ssh/id_dsa (8089890)
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /u1/dcpa/work/.ssh/identity
debug3: no such identity: /u1/dcpa/work/.ssh/identity
debug1: Trying private key: /u1/dcpa/work/.ssh/id_rsa
debug3: no such identity: /u1/dcpa/work/.ssh/id_rsa
debug1: Offering public key: /u1/dcpa/work/.ssh/id_dsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password

Regenerating the keys is NOT an option as we are using a setup that already works (with all the other machines except mine :P)

billymayday · 11-06-2008, 06:18 PM

Are you sure you copied the key correctly? What are the fist an last lines? Here's what I have

Quote:

-----BEGIN DSA PRIVATE KEY-----
Key data here in real key
-----END DSA PRIVATE KEY-----

hawk__0 · 11-06-2008, 06:30 PM

Yes I am sure. One thing that's weird though (this setup was implemented before I was working here) is that it says ssh-dss at the beginning of the key (public key, that is). isn't it supposed to be ssh-dsa? Nonetheless it's still working for the other servers that it connects to.

billymayday · 11-06-2008, 06:32 PM

What are the permissions of the key and the directory it's in?

hawk__0 · 11-06-2008, 06:36 PM

700, was previously 744 though.

I had a coworker copy me his ssh_config and sshd_config just after he set up public/private key authentication. Works fine for him. We have the same public keys too.
He is running ubuntu 8.04 and I'm running ubuntu 8.10 (Installed when it was on its final beta, in case that matters)

billymayday · 11-06-2008, 06:50 PM

~/.ssh and id_dsa should both be 600. Try that.

hawk__0 · 11-06-2008, 07:36 PM

id_rsa is 600 already

hawk__0 · 11-07-2008, 11:20 AM

bump................

hawk__0 · 11-07-2008, 01:32 PM

Fixed with chmodding my home folder (for some reason was 777, changed to 755). Deleted my .ssh folder, ssh'd localhost to recreate it, copied key back over, worked. strange indeed.

billymayday · 11-07-2008, 04:36 PM

ssh is sensitive to permissions, which is why I was asking along thos lines.