With Tera Term 4.73 I can't connect to an SSH server that sends extra debug messages in the SSH2 protocol. In my case the server is a firewall box that relays the connection and inserts some additional debug messages.
Tera Term displays an error message box saying "Unexpected SSH2 message(4) on current stage(4). DEBUG message from server: Original server fingerprint for ..." and then disconnects :-(
Here is the debug output when connecting with OpenSSH "ssh -v" client (I've highlighted the extra debug message):
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.61.60 [192.168.61.60] port 22000.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0-beta
debug1: match: OpenSSH_6.0-beta pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.8p1 Debian-7ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: DSA 6f:c3:69:7e:2b:3a:85:f3:3d:ed:09:74:4e:f4:21:66
debug1: Host '[192.168.61.60]:22000' is known and matches the DSA host key.
debug1: Found key in /root/.ssh/known_hosts:63
debug1: ssh_dss_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
*****************
debug1: Remote: Original server fingerprint for [192.168.60.13]:22000: RSA 02:82:ab:52:13:70:4f:16:1f:30:ad:37:61:3e:50:ee
*****************
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
[...]
Tera Term
With Tera Term 4.73 I can't connect to an SSH server that sends extra debug messages in the SSH2 protocol. In my case the server is a firewall box that relays the connection and inserts some additional debug messages.
Tera Term displays an error message box saying "Unexpected SSH2 message(4) on current stage(4). DEBUG message from server: Original server fingerprint for ..." and then disconnects :-(
Here is the debug output when connecting with OpenSSH "ssh -v" client (I've highlighted the extra debug message):
Can Tera Term just ignore unknown debug messages?