I created https://issues.apache.org/jira/browse/SSHD-159, but I did not attach
a patch because I figured you would want to tweak it to your liking. Simplest
would be something like:
if (!serverVersion.startsWith("SSH-2.0-") &&
(!serverVersion.startsWith("SSH-1.99"))) { throw new
Lee
> -----Original Message-----
> From: Guillaume Nodet [mailto:[email protected]]
> Sent: Tuesday, February 28, 2012 10:52 PM
> To: [email protected]
> Subject: Re: Unsupported protocol version: SSH-1.99-OpenSSH_2.9p2
>
> Yes, please raise a JIRA issue and attach your patch if you have one.
>
> On Wed, Feb 29, 2012 at 01:35, Lee Breisacher
> <[email protected]> wrote:
> > That sounds right - what do I do to make that happen? Do I need to submit a
> patch? Or can I just create a bug report?
> >
> > Thanks,
> >
> > Lee
> >
> >> -----Original Message-----
> >> From: Johnny Luong [mailto:[email protected]]
> >> Sent: Tuesday, February 28, 2012 3:24 PM
> >> To: [email protected]
> >> Subject: Re: Unsupported protocol version: SSH-1.99-OpenSSH_2.9p2
> >>
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA256
> >>
> >> On 02/28/2012 12:30 PM, Lee Breisacher wrote:
> >> > I'm using SshClient to make a simple connection to a linux box. I'm
> >> > getting the following exception:
> >> >
> >> > org.apache.sshd.common.SshException: Unsupported protocol version:
> >> > SSH-1.99-OpenSSH_2.9p2 at
> >> > org.apache.sshd.client.session.ClientSessionImpl.readIdentification
> >> > (Cl
> >> > ientSessionImpl.java:388)
> >> >
> >> >
> >> at
> >> org.apache.sshd.common.session.AbstractSession.messageReceived(Abstra
> >> ctSe
> >> ssion.java:226)
> >> >
> >> > I see this code in ClientSessionImpl>readIdentification():
> >> >
> >> > if (!serverVersion.startsWith("SSH-2.0-")) { throw new
> >> >
> >>
> SshException(SshConstants.SSH2_DISCONNECT_PROTOCOL_VERSION_NOT_SUPPO
> >> RT
> >> > ED,
> >> >
> >> >
> >> "Unsupported protocol version: " + serverVersion);
> >> > }
> >> >
> >> > So apparently the server I'm talking to supports SSH-2.0, but not
> >> > with that exact string. Is there anything I can do about this?
> >> >
> >> > Thanks,
> >> >
> >> > Lee
> >> >
> >> >
> >>
> >> Maybe all that is needed is a patch to have to 1.99 treated as 2.0,
> >> as stated in RFC 4253, 5.1.
> >>
> >> Best,
> >> Johnny
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v2.0.14 (GNU/Linux)
> >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >>
> >> iQIcBAEBCAAGBQJPTWIgAAoJENQfv1FjsMMvdU4P/RTx1loWR3Jg8iyWPC6dLFlM
> >> pZwVjb3n/Zxk1Bt8Fc9LUY3EgFpwdC0QnncYT+TulfDTH7k0FGOWEgA2qLkpGgit
> >> p7vhWIgYPXRnTzXZ7744J19EiWPrciXFk4zUfDSMizr2RDD/jW8e7Gd8Bo7gwgFh
> >> mr+dTyGKXAeDsKEoJpDf3VV1DoTtu8J/nfFuZT2fusaRqeRYz1tf6/a0BxF99baN
> >> QaJGHUctHK34A7ypVM4Gx/54tN5b5JMaO5MjjIQZxgpwlXq1f8dY8y1l0TQLOwxo
> >> vVuHDqlawidElSJGNS3+YNCp2d+fB8/2PjlWBS4mxs+mepCJ6jlgqZaWwEKpSISa
> >> v/sQpXLse/HNMt6oTxwvvFPVdu24ZgX8/KH+Qv6s32y6J3EKmqKKPZJjdmTJla0w
> >>
> rE/1KoRaQFNFZx937R5Gn/GrdRp20Y0OqdTIjGHEyShoPuuuX1CJyDrAW6QOmvvm
> >> PcNL8JXddHgvMHNbp+bUj7I9YbrP3GlnlBR7PefMGdfzG1v2ed3iDA9JryfPu+Wv
> >> 0rkfIjfRiaZ6qd3cjXkpPnTV2e5FOSpo0WYGRT8w4gc7+j7BLgziiSo6NV/cXmss
> >> zKba2CXlNrJjoZVN/7a4UyB0dLji3StYxOO/1xolaZsN7acYnuuxfW4QpiYov2nb
> >> LZ3PiYKMejrk7VJR+gnO
> >> =nkXX
> >> -----END PGP SIGNATURE-----
>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> FuseSource, Integration everywhere
> http://fusesource.com
