[rancid] Known_hosts issue with fortigate cluster

Daniel Schmidt daniel.schmidt at wyo.gov
Mon Jan 23 21:34:19 UTC 2012


Or ssh-keygen -R hostname

-----Original Message-----
From: rancid-discuss-bounces at shrubbery.net
[mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Aaron Smith
Sent: Monday, January 23, 2012 2:30 PM
To: Hugo Deprez
Cc: rancid-discuss at shrubbery.net
Subject: Re: [rancid] Known_hosts issue with fortigate cluster

On 01/23/2012 12:49 PM, Hugo Deprez wrote:
> Dear community,
>
> I just met an issue with the backup of a Fortigate 300A firewall.
> This is a cluster.
>
> Now the cluster is running on the slave member. My linux host is
> complaining about the public key which is not matching the one from
> the master.
> I would like to know how you guys, do you deal with this situation ?

If you can't manage the SSH keys on the Fortigate units, you could set
"StrictHostKeyChecking=no" in your SSH config or in the invocation of the
SSH client.

--
@@ron
_______________________________________________
Rancid-discuss mailing list
Rancid-discuss at shrubbery.net
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
E-Mail to and from me, in connection with the transaction 
of public business,is subject to the Wyoming Public Records 
Act, and may be disclosed to third parties.



More information about the Rancid-discuss mailing list