SSH host key maintenance, local provider
Andrew Wilkins
andrew.wilkins at canonical.com
Mon Oct 6 07:33:01 UTC 2014
On Fri, Oct 3, 2014 at 4:19 PM, Stuart Bishop <stuart.bishop at canonical.com>
wrote:
> On 3 October 2014 20:23, Curtis Hovey-Canonical <curtis at canonical.com>
> wrote:
> > On Fri, Oct 3, 2014 at 8:30 AM, Simon Davy <bloodearnest at gmail.com>
> wrote:
> >> On 3 October 2014 13:21, Simon Davy <bloodearnest at gmail.com> wrote:
> >>> This is what I have:
> >>>
> >>> Host 10.0.3.*
> >>> StrictHostKeyChecking no
> >>> UserKnownHostsFile /dev/null
> >>> ForwardAgent yes
> >>> LogLevel ERROR
> > ....
> >
> > Juju-CI is in several clouds. We treat the 10.* and 172.* networks as
> > ephemeral for our tests. Hp's machines on the 15.125.* are ephemeral.
> > I haven't seen enough azure and joyent IP to also ignore them.
> >
> > Host 10.*.*.* 172.*.*.* ec2-*.compute-*.amazonaws.com 15.125.*.*
> > StrictHostKeyChecking no
> > UserKnownHostsFile /dev/null
>
> Alas StrictHostKeyChecking seems the norm, which I can't use as it
> turns off port forwarding. But that UserKnownHostsFile looks
> promising...
>
"juju ssh" sets UserKnownHostsFile=/dev/null by default now. Not sure when
it was added; semi recently, probably in 1.21-alpha1.
Cheers,
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20141006/1a818c57/attachment.html>
More information about the Juju
mailing list