On Mon, Apr 28, 2008 at 11:31:34AM +0100, Mike Clarke wrote:
On Monday 28 April 2008, Anton Shterenlikht wrote:
This works fine until Node1 is down, in which case the cluster
software directs all connections to 10.10.10.1 to Node2. Since
its key doesn't match what's in known_hosts, the
On Fri, Apr 25, 2008 at 09:37:13AM -0700, Chuck Swiger wrote:
On Apr 25, 2008, at 9:09 AM, Anton Shterenlikht wrote:
Is it normal that StrictHostKeyChecking=no in .ssh/config
still refuses ssh connection when host ID has changed.
I've a setup in which host ids change frequently. How
can I
On Monday 28 April 2008, Anton Shterenlikht wrote:
This works fine until Node1 is down, in which case the cluster
software directs all connections to 10.10.10.1 to Node2. Since
its key doesn't match what's in known_hosts, the connection is
refused.
At present I tune the VMS cluster and
Is it normal that StrictHostKeyChecking=no in .ssh/config
still refuses ssh connection when host ID has changed.
I've a setup in which host ids change frequently. How
can I setup ssh so that it ignores key change.
% ssh -oPort=x xx.xx.xx.xx
On Apr 25, 2008, at 9:09 AM, Anton Shterenlikht wrote:
Is it normal that StrictHostKeyChecking=no in .ssh/config
still refuses ssh connection when host ID has changed.
I've a setup in which host ids change frequently. How
can I setup ssh so that it ignores key change.
You'd be better off
