[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-tech
Subject:    Problems with connecting SSH.com's client to a OpenSSH sshd
From:       "Karl Sjodahl - dunceor" <dunceor () gmail ! com>
Date:       2008-01-12 12:35:35
Message-ID: 5d84cb30801120435q8d49d4bse1f22e7a6782429d () mail ! gmail ! com
[Download RAW message or body]

Hello.

When updating to a new snapshot the 3rd january I discovered that
SSH.com client called SSH Secure Shell would give an error when trying
to connect to a OpenSSH sshd. It would give an error that said:
"Server responded "Protocol error: expected packet of type 30, got 2""

I did some investigation of that this morning and it's the packet.c
change that came in about 2 weeks ago, version 1.148 to 1.149 that
gives this problem.

It seems to have to do with not handling a SSH2_MSG_IGNORE message.

Applying this diff (just reversing the old patch) makes it able to
connect again.

BR
dunceor

Index: packet.c
===================================================================
RCS file: /cvs/src/usr.bin/ssh/packet.c,v
retrieving revision 1.149
diff -u -r1.149 packet.c
--- packet.c   28 Dec 2007 15:32:24 -0000    1.149
+++ packet.c   12 Jan 2008 12:27:55 -0000
@@ -1187,6 +1187,8 @@
               if (type)
                    DBG(debug("received packet type %d", type));
               switch (type) {
+              case SSH2_MSG_IGNORE:
+                   break;
               case SSH2_MSG_DEBUG:
                    packet_get_char();
                    msg = packet_get_string(NULL);
@@ -1207,7 +1209,7 @@
                    seqnr = packet_get_int();
                    debug("Received SSH2_MSG_UNIMPLEMENTED for %u",
                        seqnr);
-                   /* FALLTHROUGH */
+                   break;
               default:
                    return type;
               }

[prev in list] [next in list] [prev in thread] [next in thread]