You think on a higher level than I. My idea was something like "tickling"
bazaar.launchpad.net at install time so that the cache would be pre-loaded.
When I think about it, though, I believe that PuTTY uses the *users*
registry area, so that would not work for a multi-user situation. That means
the probe would have to be done at run time, after Bazaar realizes that it
is using launchpad. The quickest and dirtiest way to handle it would be to
patch an error message to tell the user what command to type before retrying
bzr.
I wonder if there is a plink command line switch which would make the
attempt at user interaction go away?
--
Vernon
On Thu, Nov 13, 2008 at 6:07 PM, Martin Pool <email address hidden> wrote:
> We could also add an SSHFP DNS record; see
> <http://tools.ietf.org/html/rfc4255>. I'm not sure if that would be
> trusted in practice by most users.
>
> --
> codehosting ssh host key not verifiable
> https://bugs.launchpad.net/bugs/238869
> You received this bug notification because you are a direct subscriber
> of the bug.
>
You think on a higher level than I. My idea was something like "tickling" launchpad. net at install time so that the cache would be pre-loaded.
bazaar.
When I think about it, though, I believe that PuTTY uses the *users*
registry area, so that would not work for a multi-user situation. That means
the probe would have to be done at run time, after Bazaar realizes that it
is using launchpad. The quickest and dirtiest way to handle it would be to
patch an error message to tell the user what command to type before retrying
bzr.
I wonder if there is a plink command line switch which would make the
attempt at user interaction go away?
--
Vernon
On Thu, Nov 13, 2008 at 6:07 PM, Martin Pool <email address hidden> wrote:
> We could also add an SSHFP DNS record; see tools.ietf. org/html/ rfc4255>. I'm not sure if that would be /bugs.launchpad .net/bugs/ 238869
> <http://
> trusted in practice by most users.
>
> --
> codehosting ssh host key not verifiable
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>