ssh without a password

From: Bill K. (bilkay0@yahoo.com)
Date: 01/01/02 

From: "Bill K." <bilkay0@yahoo.com>
Date: Tue, 01 Jan 2002 09:11:47 -0500

When I first installed all the openssh rpms, I was able to ssh without a
password by following the man page. Somewhere along the line, I was
experiencing some network difficulty (I didn't completely know what I was
doing - and still don't), and I got a message that a host key had changed.
After that, I couldn't do anything without a password. I'm pretty sure
whatever happened wasn't a security breach because there wasn't an
opportunity during the time between when it worked and when it didn't.

I even tried uninstalling and reinstalling all the rpms, and deleting the
contents of the ~/.ssh directories, but it didn't make any difference.

ssh -v {Host} output:

OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Seeding random number generator
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 Neptune [192.168.1.1] port 22.
 debug1: temporarily_use_uid: 500/500 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 500/500 (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/{user}/.ssh/identity type 0
debug1: identity file /home/{user}/.ssh/id_rsa type -1
debug1: identity
file /home/{user}/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_2.9p2
debug1: match: OpenSSH_2.9p2 pat ^OpenSSH Enabling compatibility mode for protocol 2.0 debug1: Local
version string SSH-2.0-OpenSSH_2.9p2
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: 132/256
debug1: bits set: 1014/2049
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'neptune' is known and matches the RSA host key.
debug1: Found key in /home/{user}/.ssh/known_hosts2:1
debug1: bits set: 965/2049
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/{user}/.ssh/id_rsa
debug1: try privkey: /home/{user}/.ssh/id_dsa
debug1: next auth method to try is password

I've tried running ssh-keygen to files id_rsa and id_dsa and copying the
keys to /$HOME/.ssh/authorized_keys2 on the remote PC, and it still
demands a password (and ssh -v optput is the same except the 2nd and 3rd
last lines are gone).

How do I get back to being able to ssh without a password?

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)
  • Re: Problems with scp and cron
    ... default names in .ssh directory. ... debug1: read PEM private key done: type ... When I run the script manually, ssh finds the identification file in .ssh2/ ...
    (comp.security.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)
  • Re: cant connect, ssh hangs after SSH2_MSG_KEX_DH_GEX_GROUP
    ... Looks like the sshd is not getting the ssh key request from the client ... debug1: Connecting to server port 22. ... debug1: read PEM private key done: type DSA ...
    (SSH)
  • New S10 system does not accept ssh from other hosts
    ... debug1: read PEM private key done: type RSA ... debug1: private host key: #0 type 1 RSA ... When I try to ssh in, or even telnet to port 22, from ...
    (comp.unix.solaris)