marekm at diament.ists.pwr.wroc.pl
2000-Nov-30 15:41 UTC
Problem talking to SSH 2.3.0 server
I'd like to report a problem I found with the OpenSSH client talking to the SSH 2.3.0 server. client: i686-pc-linux (Debian 2.2, kernel 2.2.18pre19, glibc-2.1.3), SSH-2.0-OpenSSH_2.3.0p1 (built by me from source, but the same problem occurs with ssh_2.2.0p1-1.1 as shipped with Debian 2.2). server: sparc-sun-solaris2.7, SSH-2.0-2.3.0 SSH Secure Shell (non-commercial) Problem: some time after logging into the server (few minutes to few hours, happens even if the session is mostly idle), I get this error message: Hm, dispatch protocol error: type 20 plen 136 and no more data can be received from the server (the other direction appears to be OK - the server gets the commands I type, but I can't see them echoed back). The ~. escape closes the connection as it should. Thanks, Marek PS. Yes, I will try to convince the admin of that server to install OpenSSH instead.
On Thu, 30 Nov 2000 marekm at diament.ists.pwr.wroc.pl wrote:> server: sparc-sun-solaris2.7, > SSH-2.0-2.3.0 SSH Secure Shell (non-commercial) > > Problem: some time after logging into the server (few minutes to few > hours, happens even if the session is mostly idle), I get this error > message: > > Hm, dispatch protocol error: type 20 plen 136 > > and no more data can be received from the server (the other direction > appears to be OK - the server gets the commands I type, but I can't see > them echoed back). The ~. escape closes the connection as it should.Perhaps this is related to rekeying feature in ssh.com SSH? If this is the case, setting 'RekeyIntervalSeconds 0' in sshd2_config might help. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
On Thu, 30 Nov 2000 marekm at diament.ists.pwr.wroc.pl wrote:> Hm, dispatch protocol error: type 20 plen 136 > > and no more data can be received from the server (the other direction > appears to be OK - the server gets the commands I type, but I can't see > them echoed back). The ~. escape closes the connection as it should.IIRC, you need to disable rekeying on the server end. -d -- | ``We've all heard that a million monkeys banging on | Damien Miller - | a million typewriters will eventually reproduce the | <djm at mindrot.org> | works of Shakespeare. Now, thanks to the Internet, / | we know this is not true.'' - Robert Wilensky UCB / http://www.mindrot.org