ssh no longer connecting automatically

Dag-ErlingSmørgrav des at des.no
Thu Mar 25 04:38:04 PST 2004


Jonathon McKitrick <jcm at FreeBSD-uk.eu.org> writes:
> On Sat, Feb 21, 2004 at 03:52:27PM -0500, Christian W. Sung wrote:
> : 2. Copy the resulting id_rsa.pub to ~/.ssh/authorized_keys2 on the
> : remote machine you're trying to access, and if there's an
> : authorized_keys (without the ending 2), copy the key there as well.

There is no difference between authorized_keys and authorized_keys2
except the name.  There is no point in having both.

> neptune:~> ssh jcm at dogma.freebsd-uk.eu.org
> The authenticity of host 'dogma.freebsd-uk.eu.org (130.88.200.97)' can't be
> established.
> DSA key fingerprint is c4:81:d6:8d:48:0e:39:ba:b3:40:e2:52:62:18:d4:f5.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'dogma.freebsd-uk.eu.org,130.88.200.97' (DSA) to
> the list of known hosts.
> key_verify failed for server_host_key

Something's wrong with your .ssh/known_hosts.  Running ssh with one or
more -v may give an indication of exactly what is wrong.

DES
-- 
Dag-Erling Smørgrav - des at des.no


More information about the freebsd-stable mailing list