want an option to ssh using facilities to control knownhosts

[Robert Collins]

It would be nice when talking to ec2 instances, or other dynamically
created hosts to not have to worry about known_hosts; there are various
tricks that can be done with different ssh clients. We should have a
means when getting an ssh transport to specify that this should be done.

 affects bzr

[Martin Pool (mbp)]

I'm not really convinced this belongs inside bzr; it's more user policy than something we know about.

For the user, it should be possible to set something like this in ~/.ssh/config

Host *.ec2.amazonaws.com
   StrictHostKeyChecking no

(domain name may be wrong, untested.)

[Robert Collins (lifeless)]

On Thu, 2009-04-09 at 04:39 +0000, Martin Pool wrote:
> I'm not really convinced this belongs inside bzr; it's more user policy
> than something we know about.

Its code policy when code knows, so there is no reason not to put it in
bzr.

> For the user, it should be possible to set something like this in
> ~/.ssh/config
>
> Host *.ec2.amazonaws.com
> StrictHostKeyChecking no
>
> (domain name may be wrong, untested.)

No, this doesn't work. You need command line options to ssh to make it
use /dev/null as the hostkey file.

Also this isn't for the 'ssh transport', its for

 summary want an option to ssh using facilities to control knownhosts

[Robert Collins (lifeless)]

On Thu, 2009-04-09 at 04:39 +0000, Martin Pool wrote:
> I'm not really convinced this belongs inside bzr; it's more user policy
> than something we know about.

Its code policy when code knows, so there is no reason not to put it in
bzr.

> For the user, it should be possible to set something like this in
> ~/.ssh/config
>
> Host *.ec2.amazonaws.com
> StrictHostKeyChecking no
>
> (domain name may be wrong, untested.)

No, this doesn't work. You need command line options to ssh to make it
use /dev/null as the hostkey file.

Also this isn't for the 'ssh transport', its for

 summary "want an option to ssh using facilities to control knownhosts"