General discussion about Chef

[chef] Re: knife ec2 create, ssh hostkey mismatch


Chronological Thread 
  • From: Sean OMeara < >
  • To:
  • Subject: [chef] Re: knife ec2 create, ssh hostkey mismatch
  • Date: Mon, 29 Nov 2010 11:32:58 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ZldncV8MkjhUe9xlwgDqRIDhdCLBoPD6C0gpwE5s9fyrSzsqTRqN1xnhrxka70hGEv 4+8TcvWpTo45J8WmUsaBAXIvYHT/FRpZvWuPBaWsMTNQz9yKjjE0RimvIQSaJXHhJked 6a/WDtNJjkLBPP5Lrp6hqa6HnFNrOg/DVrrUg=
navi:~$ cat ~/.ssh/config
ForwardAgent yes

Host *.amazonaws.com
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null


On Mon, Nov 29, 2010 at 11:21 AM, Simon Detheridge 
< >
 wrote:
> Hi,
>
> When regularly starting new servers with knife ec2 create, sometimes a 
> server grabs an IP address already used by an older one and knife fails to 
> bootstrap as it fails host key check on ssh connect.
>
> Given strict host key checking is off anyway (i.e. it doesn't prompt me to 
> accept the host key on first connect) is it also possible to prevent 
> writing the new host key to known_hosts, so this doesn't keep happening?
>
> Thanks,
> Simon
>
> --
> Simon Detheridge - CTO, Widgit Software
> 26 Queen Street, Cubbington, CV32 7NA - Tel: +44 (0)1926 333680
>

Archive powered by MHonArc 2.6.16.

§