No subject

eskimo.com into your known hosts file.

Two ways to do that:

Get the admin to send them to you 

Answer yes to the question about the authenticity of the host.

One of these methods is easy and not so safe, the other is not so easy
(depending on the mood/competency of the admin) and a little safer.

Hugh


"Rob Mohr"
> 
> Question, does the Rhosts Auth disabled, is that the nexus of my problem?
> eof
> 
> OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
> debug1: Reading configuration data /usr/local/etc/ssh_config
> debug1: Seeding random number generator
> debug1: Rhosts Authentication disabled, originating port will not be trusted.
> debug1: restore_uid
> debug1: ssh_connect: getuid 0 geteuid 0 anon 1
> debug1: Connecting to eskimo.com [204.122.16.13] port 22.
> debug1: temporarily_use_uid: 0/0 (e=0)
> debug1: restore_uid
> debug1: temporarily_use_uid: 0/0 (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 /root/.ssh/identity type -1
> debug1: identity file /root/.ssh/id_rsa type -1
> debug1: identity file /root/.ssh/id_dsa type -1
> debug1: Remote protocol version 1.5, remote software version 1.2.27
> debug1: no match: 1.2.27
> debug1: Local version string SSH-1.5-OpenSSH_2.9p2
> debug1: Waiting for server public key.
> debug1: Received server public key (768 bits) and host key (1024 bits).
> The authenticity of host 'eskimo.com (204.122.16.13)' can't be established.
> RSA1 key fingerprint is f8:6c:e7:b0:3c:cb:5e:8a:aa:4e:10:1c:33:87:e6:cf.
> Are you sure you want to continue connecting (yes/no)? Aborted by user!
> debug1: Calling cleanup 0x80630cc(0x0)