As a follow up to my own post:
> The only known_hosts file that exists on the machine is in
> /root/.ssh/known_hosts which does not have a problem
> connecting. So I figured rather than properly diagnose this,
> I'd make it work again since I'm starting to run against time
> constraints...too
Thanks for all the info! Regretibly, I'm still having problems...
> My guess is that when you did your re-install you didn't
> backup and restore the host keys for your machine. That
> means that all of the accounts on systems you've been
> connecting to will have the old host keys in the
> $
On Sun, Feb 23, 2003 at 07:23:57PM -0500, John Straiton wrote:
> Greets,
> I have many times set up the authorized_keys so that remote
> ssh/scp/rsync clients can connect between machines without a password.
> However, in attempting to do this again using a 5.0-RELEASE machine
> trying to con
Greets,
I have many times set up the authorized_keys so that remote
ssh/scp/rsync clients can connect between machines without a password.
However, in attempting to do this again using a 5.0-RELEASE machine
trying to connect to a 4.7 machine, I'm getting nothing but:
%ssh 192.168.0.23
Host
