ssh key doesn't work



Sashi
View profile
More options Aug 21, 4:31 pm
Newsgroups: comp.unix.shell
From: Sashi <small...@xxxxxxxxx>
Date: Tue, 21 Aug 2007 13:31:56 -0700
Local: Tues, Aug 21 2007 4:31 pm
Subject: ssh key generation help
Reply | Reply to author | Forward | Print | Individual message | Show
original | Remove | Report this message | Find messages by this author
Hi All, I need some help with setting up my ssh keys.

On one machine (let's call it client), I've generated my ssh keys
thus:
ssh-keygen -t rsa
Then I copied over the public part to the other machine (let's call it
the host).
I copied it over to ~/.ssh/authorized_keys.

When I try to ssh from client to host, I'm still being promted for a
password.
I've googled around and it looks like I've followed the proper steps.
Not sure what I'm missing here.

When i do an ssh -v, I see the following:
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to host port 22.
debug1: Connection established.
debug1: identity file /home/user/.ssh/identity type -1
debug1: identity file /home/user/.ssh/id_rsa type 1
debug1: identity file /home/user/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version 4.4.6.43
SSH Secure Shell
debug1: no match: 4.4.6.43 SSH Secure Shell
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-Sun_SSH_1.1
debug1: Failed to acquire GSS-API credentials for any mechanisms (No
credentials were supplied, or the credentials were unavailable or
inaccessible
Unknown code 0
)
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: Peer sent proposed langtags, ctos:
debug1: Peer sent proposed langtags, stoc:
debug1: We proposed langtags, ctos: i-default
debug1: We proposed langtags, stoc: i-default
debug1: dh_gen_key: priv key bits set: 135/256
debug1: bits set: 514/1024
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host 'host' is known and matches the DSA host key.
debug1: Found key in /home/user/.ssh/known_hosts:1
debug1: bits set: 511/1024
debug1: ssh_dss_verify: signature correct
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: got SSH2_MSG_SERVICE_ACCEPT

Can someone please tell me what I'm missing here?
Thanks,
Sashi

.

Relevant Pages

  • RE: RE : RE : X11Forwarding problem on Solaris.
    ... The program is using the display environment variable. ... First i use ssh to connect from node2 to node4 and then I start the PROGRAM ... debug1: Connection established. ... Subject: RE: RE: X11Forwarding problem on Solaris. ...
    (SSH)
  • OpenSSH slow to establish connections
    ... I am experiencing problems with connecting to a host on the LAN via SSH. ... debug1: Remote protocol version 2.0, ... the connection is established pretty quickly. ...
    (SSH)
  • Solaris->Fedora6 unidirectional problem
    ... I have a strange unsolved unidirectional problem using ssh from Solaris to Fedora6: ... I have a couple FC6 behind the Solaris boxes ... debug2: fd 4 setting O_NONBLOCK ... debug1: fd 4 clearing O_NONBLOCK ...
    (SSH)
  • [SLE] Slow SSH login
    ... A> ssh B ... second delay no matter the authentication mechanism ... debug1: Authentication succeeded. ...
    (SuSE)
  • Re: Cant login using ssh; no password prompt
    ... I also had accessed other hosts form there using ssh. ... >debug1: Connection established. ... Remote protocol version 2.0, ... Host 'workbench.blstar' is known and matches the DSA host key. ...
    (freebsd-questions)