Date: Mon, 28 Apr 2008 11:31:34 +0100 From: Mike Clarke <jmc-freebsd@milibyte.co.uk> To: freebsd-questions@freebsd.org Cc: Anton Shterenlikht <mexas@bristol.ac.uk> Subject: Re: ssh StrictHostKeyChecking=no refuse connection when key changed Message-ID: <200804281131.35233.jmc-freebsd@milibyte.co.uk> In-Reply-To: <20080428093759.GA71558@mech-aslap33.men.bris.ac.uk> References: <20080425160939.GA9863@mech-aslap33.men.bris.ac.uk> <EA92F240-7932-42CB-A669-F63942EDD3D4@mac.com> <20080428093759.GA71558@mech-aslap33.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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 reboot individual nodes > frequently. I'd like to be able to tell ssh to ignore key mismatch > at this stage. Just a quick, and untested, thought. Could you use the same key files on all the nodes in the cluster? It might work unless ssh on the local machine objects to machines having identical keys in the known_hosts file. -- Mike Clarke
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200804281131.35233.jmc-freebsd>