Comment 17 for bug 414743

Martin Pool пишет:
> 2009/9/3 Alexander Belchenko <email address hidden>:
>> John A Meinel пишет:
>>> Note that Alexander's change doesn't actually make Paramiko the default,
>>> for people like me who have cygwin installed and thus have a valid 'ssh'
>>> implementation on the path. For this, you have to still specify
>>> "BZR_SSH=paramiko" as an environment variable.
>> I want only exclude plink from the game. I have no real experience (neither good or bad) with
>> cygwin+ssh.
>>
>>> Not to mention that if we switch more to GUI level apps, then we can
>>> have QBzr give a password prompt, rather than having it show up on a
>>> terminal.
>> Yes, we have similar confusion even from Linux people, see bug
>> https://bugs.launchpad.net/bugs/422656
>>
>> Actually I'd like to go even further and suggest using paramiko as default client even on Linux, at
>> least with GUI tools.
>
> I think that gets more into the case that I was trying to explain
> above: people on unix have openssh-specific configuration. For
> instance I have an 89-line long .ssh/config, and without the proxy
> configuration and other stuff in it I can't connect to several
> machines. The impact of switching to paramiko would then be: are the
> features I need still available there, and if not, is it reasonably
> discoverable that I should switch back to external ssh. But I think
> that's potentially resolvable.

OK, this is very valuable example. As I said before I have no experience with OpenSSH nor with
complex ssh configs. Of course your case change the status quo. So I no more blindly believe that
paramiko is the best.

> I will also mention that there is a way to get ssh to use an external
> program to ask for passwords or passphrases, and we could try to hook
> into that. Whether it will give us such nice integration, and whether
> it's worth writing that code for both paramiko and openssh is
> questionable.

So we have stalemate situation. And this is frustrating. :-/