In TinyTERM Plus, set up an SSH connection and connect. The fingerprint dialog comes up and asks if you want to continue. If you click Yes, the original session doesn’t connect. Instead, a second session opens and brings up the username/password dialog. Enter your username and password, and this session connects. The first session does not connect initially, but will connect normally if you go back to it.

CR 428, fixed in TinyTERM 4.30

Connecting to a host running sshd version 3.2, TinyTERM Plus returns the error, “Error verifying key.” It works properly with older sshd daemons. This is fixed in TinyTERM Plus 4.30.

CR 411

The SSH connection type allows you to choose from four encryption methods: None, DES, Blowfish and Triple DES. Only the latter two work in TinyTERM Plus versions prior to 4.30.

CR 356

When TinyTERM closes automatically, some versions produce the error, “CSL Run Engine ActiveX DocObject Server has encountered a problem and needs to close.” The details for the error message show: Faulting application tt.exe, faulting module cente.ocx. This happens if Establish connection on open, Close session on disconnect and exit, and Login at connect are set in the Session Properties. Turning off Close session on disconnect and exit fixes the problem.

CR 327, fixed in TinyTERM 4.30

TinyTERM 4.x gives garbage or no response over a 7-bit connection, particularly if even parity is set. This was fixed in TinyTERM 4.21.

CR 323

Fingerprint for SSH connections was added in TinyTERM Plus 4.21. TinyTERM 4.21 also includes the addition of proxy services for connecting through firewalls.

CR 305

The available baud rates in TERM for UNIX/Linux were extended to allow 57600 and 115200 in version 6.28.

CR 221

When TinyTERM Plus is connected via SSH, the Status Bar reads, “Connected = Telnet.” There is no patch for this. It was fixed in TinyTERM Plus 4.20.

CR 183

In TinyTERM versions prior to 4.21, if there is a Winsock problem, you have to wait for TinyTERM to time out before you can do anything. TinyTERM 4.21 allows for an instant disconnect, regardless of the state of Winsock.

CR 170

When using the Delete key to interrupt a UNIX process, such as a long directory listing, a telnet connection hangs. You have to disconnect and reconnect. This is fixed in TinyTERM 4.13.

CR 163