openssh unix dev - Jul 2002 - [Bug 368] New: TTSSH will not connect to OpenSSH_3.4p1

http://bugzilla.mindrot.org/show_bug.cgi?id=368

           Summary: TTSSH will not connect to OpenSSH_3.4p1
           Product: Portable OpenSSH
           Version: -current
          Platform: ix86
        OS/Version: NetBSD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sshd
        AssignedTo: openssh-unix-dev at mindrot.org
        ReportedBy: mindrot at regs.nebcorp.com


The popular TeraTerm TTSSH ssh client is having problems connecting to sshd.  

TTSSH will throw a dialog box with the message:

"Detected corrupted data; connection terminating."

"Detected corrupted data; connection terminating."

... and then exit. Pretty annoying.

Here's debugging output:

debug1: sshd version OpenSSH_3.4p1
debug1: private host key: #0 type 0 RSA1
debug3: Not a RSA1 key file /usr/pkg/etc/ssh/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug3: Not a RSA1 key file /usr/pkg/etc/ssh/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: Bind to port 2222 on ::.
Server listening on :: port 2222.
debug1: Bind to port 2222 on 0.0.0.0.
Server listening on 0.0.0.0 port 2222.
Generating 768 bit RSA key.
RSA key generation complete.
debug1: Server will not fork when running in debugging mode.
Connection from 192.168.0.4 port 4910
debug1: Client protocol version 1.5; client software version TTSSH/1.5.4 Win32
debug1: no match: TTSSH/1.5.4 Win32
debug1: Local version string SSH-1.99-OpenSSH_3.4p1
debug2: Network child is on pid 18843
debug3: preauth child monitor started
debug3: mm_request_receive entering
debug3: privsep user:group 16:16
debug1: Sent 768 bit server key and 1024 bit host key.
debug1: Encryption type: blowfish
debug3: mm_request_send entering: type 28
debug3: monitor_read: checking request 28
debug3: mm_request_receive_expect entering: type 29
debug3: mm_request_receive entering
debug3: mm_request_send entering: type 29
debug3: mm_ssh1_session_id entering
debug3: mm_request_send entering: type 30
debug1: Received session key; encryption turned on.
debug2: monitor_read: 28 used once, disabling now
debug3: mm_request_receive entering
debug3: monitor_read: checking request 30
debug3: mm_answer_sessid entering
debug2: monitor_read: 30 used once, disabling now
debug3: mm_request_receive entering
debug1: Installing crc compensation attack detector.
Disconnecting: Corrupted check bytes on input.
debug1: Calling cleanup 0x80678c0(0x0)
debug1: Calling cleanup 0x80678c0(0x0)

The machine running it: 

regs at vietnam|~% uname -a
NetBSD vietnam.doof.nebcorp.com 1.5.2 NetBSD 1.5.2 (GENERIC) #3: Sat Aug 18 
23:37:05 CEST 2001     
he at hamster.urc.uninett.no:/usr/src/sys/arch/i386/compile/GENERIC i386


And an OpenBSD machine running the non-portable server works fine:

debug1: sshd version OpenSSH_3.4
debug1: private host key: #0 type 0 RSA1
debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: Bind to port 2222 on ::.
Server listening on :: port 2222.
debug1: Bind to port 2222 on 0.0.0.0.
Server listening on 0.0.0.0 port 2222.
Generating 768 bit RSA key.
RSA key generation complete.
debug1: Server will not fork when running in debugging mode.
Connection from 64.81.49.197 port 57869
debug1: Client protocol version 1.5; client software version TTSSH/1.5.4 Win32
debug1: no match: TTSSH/1.5.4 Win32
debug1: Local version string SSH-1.99-OpenSSH_3.4
debug2: Network child is on pid 29316
debug3: preauth child monitor started
debug3: mm_request_receive entering
debug3: privsep user:group 32767:32767
debug1: Sent 768 bit server key and 1024 bit host key.
debug1: Encryption type: blowfish
debug3: mm_request_send entering: type 28
debug3: monitor_read: checking request 28
debug3: mm_request_receive_expect entering: type 29
debug3: mm_request_receive entering
debug3: mm_request_send entering: type 29
debug3: mm_ssh1_session_id entering
debug3: mm_request_send entering: type 30
debug1: Received session key; encryption turned on.
debug2: monitor_read: 28 used once, disabling now
debug3: mm_request_receive entering
debug3: monitor_read: checking request 30
debug3: mm_answer_sessid entering
debug2: monitor_read: 30 used once, disabling now
debug3: mm_request_receive entering
debug1: Installing crc compensation attack detector.
debug3: mm_getpwnamallow entering
debug3: mm_request_send entering: type 6
debug3: monitor_read: checking request 6
debug3: mm_answer_pwnamallow
debug3: mm_answer_pwnamallow: sending MONITOR_ANS_PWNAM: 1
debug3: mm_request_send entering: type 7
...

Any ideas?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.