[kdo at cosmos.phy.tufts.edu: protocol incompatibility between OpenSSH and SSH secure shell?]
Ken Olum
kdo at cosmos.phy.tufts.edu
Wed Jan 3 04:34:14 EST 2001
From: Markus Friedl <markus.friedl at informatik.uni-erlangen.de>
Date: Fri, 29 Dec 2000 23:22:01 +0100
openssh does not support rekeying (yet). perhaps openssh-2.5 will,
openssh-2.4 will not.
What is the connection between rekeying and forwarding of
user-specified ports?
upgrading the windows client to ssh.com-2.4.0 should help.
It did not.
On Fri, Dec 29, 2000 at 04:13:53PM -0500, Michael H. Warfield wrote:
> Hello all!
>
> I didn't see anyone else reply to this, but I also didn't see
> anything show up on the OpenSSH development list (Cc'ed here). There
> is a patch call out right now for the pending release of 2.4.0. I'm
> wondering if anyone is aware of this and if it's already been covered
> in 2.4.0?
>
> Please reply to list and original poster...
>
> ----- Forwarded message from Ken Olum <kdo at cosmos.phy.tufts.edu> -----
>
> Date: Wed, 27 Dec 2000 16:19:20 -0500
> From: Ken Olum <kdo at cosmos.phy.tufts.edu>
> To: ssh at clinet.fi
> Subject: protocol incompatibility between OpenSSH and SSH secure shell?
> Precedence: bulk
>
> I am using SSH secure shell version 2.3 under Windows 95 as the
> client and OpenSSH_2.3.0p1 under Red Hat 7.0 as the server. When I
> tell the client to forward a random incoming port the server gives the
> error "error: Hm, dispatch protocol error: type 80 plen 33" instead of
> listening on my port.
>
> Sorry if this is the wrong place to report this, or if I should have
> looked in some list of known problems.
>
> Ken Olum
>
> ----- End forwarded message -----
>
> Mike
> --
> Michael H. Warfield | (770) 985-6132 | mhw at WittsEnd.com
> (The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/
> NIC whois: MHW9 | An optimist believes we live in the best of all
> PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
>
>
More information about the openssh-unix-dev
mailing list