- From: Jonathan Matthews <
>
- To:
- Subject: [chef] Re: Re: knife ec2 create, ssh hostkey mismatch
- Date: Mon, 29 Nov 2010 22:20:58 +0000
On 29 November 2010 16:32, Sean OMeara
<
>
wrote:
>
navi:~$ cat ~/.ssh/config
>
ForwardAgent yes
>
>
Host *.amazonaws.com
>
StrictHostKeyChecking no
>
UserKnownHostsFile=/dev/null
The solution to hitting yourself in the knackers with a hammer is not
to look away and hope it stops, the solution is to put the hammer down
and move away to a safe distance. Fix the /problem/. (Yes, I know
this was a reply to a direct question, but sometimes the question is
so wrong it can't be answered in the form it's asked :-))
Either store a definitive list of host keys and construct your
known_hosts file pragmatically, or devise a way to remove entries when
instances are terminated. Don't simply eschew an important part of the
layered security that using ssh gives you. It's not just about
encryption.
Jonathan
--
Jonathan Matthews
London, UK
http://www.jpluscplusm.com/contact.html
Archive powered by MHonArc 2.6.16.