If you look at the top of the file, during the TCP_SEND in an SSH connection TinyTERM Plus sends over the DH_GEX with SHA1. This excludes DH_GEX SHA256, a replacement standard for the SHA1 variant.

Newer versions of SSH require this by default. Keys generated with this requirement won’t import correctly into TinyTERM. They can’t be verified.

CR 805

Century Software, Inc., has had a request for direct USB connectivity in TinyTERM. This would not be through a USB-to-serial adapter or anything similar. This would be a direct USB port connection between TinyTERM and the host system.

CR 803

SCO OpenServer 6 addresses serial ports with /dev/term/XX numbering. TERM for SCO UNIX’s callin and callout routines require /dev/ttyNN format instead. While SCO OpenServer 6 also provides that format for serial ports, it’s not their preferred method.

CR 794

Generate an RSA key through any method, then copy it to the PC. Load the key in TinyTERM and supply the username & hostname as normal. TinyTERM still asks for both username and password on connect, as though RSA key was not there.

This happens because the hka= and hkafile= keys in the .tpx file aren’t set when you use an RSA key. The key is ignored because it’s not written to the .tpx. But manually editing the information into the .tpx file doesn’t always work either.

CR 788

When using telnet to connect to an IBM mainframe running VSC or VSE, TinyTERM’s TN3270 emulation connects, then immediately disconnects with no errors. The mainframe log shows a variant on one of the following errors, depending on which version of TCP/IP is installed:

TEL911E TN3270 negotiation error type askterm.

TEL967E Negotiation error: Expected FFFB18 received null.

TinyTERM on the same PC has no problems connecting to a mainframe running VM.

CR 776, fixed in TinyTERM Plus 4.7.1, 24 January 2012

TinyTERM does not pass on modem error messages received via TAPI. This makes it difficult to determine what’s happening when a modem connection fails. For example:

1. Dial a known busy number. (It’s easiest to call the same line TinyTERM is using to dial.) You can hear the modem dial and get a busy signal, but TinyTERM displays no errors. It shows as disconnected the whole time, though a “busy” message should pop up.
2. Dial a line and don’t answer it. You’ll hear the modem dial and the line ringing. TinyTERM shows as disconnected until it hangs up. The expected “no answer” message doesn’t come up.

CR 757, fixed in TinyTERM 4.65

TinyTERM will not dial the Best Data 56USB-P modem on Windows XP. All other applications can successfully use the modem.

CR 745

PIXIL Thin Client only connects over TCP/IP. Century Software, Inc., has had a request to allow the included xterm to connect via direct serial cable.

CR 744

Set up a Citrix connection, either in the Citrix ICA Client or the PIXIL Login Manager. You can select the Launch configuration on startup option, but it doesn’t work. It fails even if the Citrix session is the only session listed.

CR 736

Currently port forwarding in TinyTERM Plus does local-to-remote and remote-to-local forwarding. Century Software, Inc., has had a request  to use TinyTERM Plus as a sort of “go-between” from the SSH server to another system, encrypting on the way. This would requires a third, indirect port forwarding option be added to TinyTERM Plus.

CR 729