bzr doesn't support lsh...

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alfred M. Szmidt wrote:
> [please CC, I am not subscribed]
> 
> GNU bzr doesn't support lsh, the GNU implementation of the secure
> shell protocol, this is a pitty, since bzr is also a GNU project
> 
> ams at beryx:~/s$ BZR_SSH=lsh bzr branch bzr+ssh://foo.gnu.org/bar/
> bzr: ERROR: Unrecognised value for BZR_SSH environment variable: lsh
> 
> It seems that bzr hardcodes all possible permutations of what is
> possible, most programs allow any kind of input, this is useful for
> testing, or using other remote shells (one could want to use rsh for
> example).
> 
> I am not versed in Python, would someone like to voluenteer to fix
> this issue?
> 
> 

Does 'lsh' take the same arguments as other SSH implementations?

That's probably the reason why they are hardcoded, as we don't actually
just spawn 'ssh', but spawn either:


 ssh -oForwardX11=No -oForwardAgent=no -oClearAllForwardings=yes \
     -oProtocol=2 -oNoHostAuthenticationForLocalhost=yes \
     [-p $PORT] [-l $USERNAME] [-s $SUBSYSTEM] \
     $COMMAND

versus

 ssh -x \
     [-p $PORT] [-l $USERNAME] [-s $SUBSYSTEM] \
     $COMMAND

versus

  plink -x -a -ssh -2 -batch \
     [-P $port] [-l $USERNAME] [-s $SUBSYSTEM] \
     $COMMAND

Note that is '-P' for plink, versus '-p' for the other two, and mostly
just extra arguments.

Anyway, because of that, we need to know the specific program to run, so
that we know what arguments to supply to that, as all "SSH"
implementations are not equal.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoHoBoACgkQJdeBCYSNAAMHCACg0jTjYsikr8nJcEKEob5ZJy4D
8BkAn3XYC1vbXGiFlECI9/XUkJnJPXwe
=n6n8
-----END PGP SIGNATURE-----