There are two main causes for this error. The first is an error in the fingerprint.

To remove the fingerprint in Windows, open the Registry Editor and go to HKEY_CURRENT_USER\Software\Century Software\HostKeys. Delete all the entries inside that folder, but leave the folder itself there, then close the Registry Editor. The next time you start TinyTERM and connect to that host, it will ask if the fingerprint is correct. Click Yes and continue.

To remove the fingerprint in UNIX, go to the user’s home directory and enter the command:

cd .ssh

In that directory you’ll find a known_hosts file. Rename that and attempt the connection again.

If that does not clear the problem up, the host is probably configured to accept RSA key authentication, but TinyTERM or TERM is using a username and password instead. To disable RSA on the host, go to its /etc/ssh directory and edit the sshd_config file. Look for the following two lines:

RSAAuthentication yes
PubkeyAuthentication yes

Change “yes” to “no” on each line. The lines may also be commented out with the # character. If so, remove it from the beginning of the line when making the change. Restart the SSH daemon after making the change.

CR 662
CR 802, request for option to continue on failed host key

Port forwarding, or tunneling, is a way to forward normally non-secure TCP/IP traffic through an SSH connection. You would normally need it any time you have traffic over a public network, such as the Internet, that you don’t want anyone to snoop on. More information is available elsewhere on our website.

To set it up in TinyTERM version 4.3 or higher, do the following:

1. Open a new session in TinyTERM.
2. Click on the Edit menu and select Session Properties.
3. Change the connection type to SSH and click the Apply button.
4. Click on the Port Forwarding tab.
5. Enter a name for the connection.
6. Choose whether to forward a local TCP/IP port to a remote host (Local to remote forwarding), or forward a remote port to the local PC (Remote to local forwarding).
7. Enter the local port that will forward or receive forwarding.
8. If the SSH server is not the remote system, check the “Remote host is different machine from SSH server machine” box and enter the hostname or IP address of the SSH server.
9. Enter the TCP/IP port for the remote host.
10. Enter the name of the local PC application to run, or click the Browse button to select one. Enter any command-line parameters for the local PC application.
11. Click the Add button to add the connection to the list.

The next time you open this TinyTERM session, the port forwarding you set up will be active. Sample application setups are available here.

CR 385, added in TinyTERM Plus 4.30

SSH (Secure SHell) is a replacement for telnet and rlogin. It encrypts all data transmissions between the terminal and the host, rather than sending them in plain text.

When connecting to a host over the Internet, the data transmissions are available to anyone with the technical knowhow to tap into them. Telnet and rlogin send data in plain text, so they can easily be read. This could compromise proprietary or confidential information.

With SSH, the data transmissions are encrypted. Even if someone manages to hack into your connection, the information is in a format readable only by your PC and the remote host. This helps protect your valuable information from unauthorized access.

TinyTERM Plus, TinyTERM Thin Client and TinyTERM Web Server all include SSH from versions 4.10 on. (TinyTERM Thin Client was combined with TinyTERM Plus in version 4.40.) TERM for UNIX version 6.28 also includes SSH.

You will also need an SSH daemon on your host computer. You can download this program from http://www.openssh.org/ at no cost.

In TinyTERM version 4.x for Windows, you can have multiple IP addresses or telephone numbers in one .tpx file. For each phone number or address you want to use, open the Session Properties and enter it in the “Host name, IP address or phone number” line. Click OK, then save the session. Repeat this until you have entered them all. Make sure “Establish connection on open” is not checked.

To choose from the listed numbers, open the Session Properties. The “Host name, IP address or phone number” line will be a drop-down list, showing your multiple addresses and phone numbers. Select the one you want, then click OK. Connect as usual.

If you do not save a username and password in the Session Properties of TinyTERM Plus, it will pop up a dialog box requesting them when you connect. However, if TinyTERM is configured to save settings on exit, or if you click Yes when asked to save the session, TinyTERM saves the login information automatically.

In TinyTERM Plus versions prior to 4.31, this will happen even if TinyTERM Plus is configured never to save settings on exit. This bug was fixed in TinyTERM Plus 4.31.

To prevent this in TinyTERM Plus 4.31 and higher versions, go to TinyTERM Plus’ Edit menu and select Preferences. Under Save settings on exit, select the Never radio button. You can also choose the Protect all settings option, which will prevent any changes from being saved as long as it is set.

CR 479, fixed in TinyTERM Plus 4.31
CR 640

Using TinyTERM 4.2, transparent printing will skip pages at random. This is due to a bug in SSH communications. To fix it, download this patch. Unzip it into a temporary directory. Three files will be extracted:

regall.bat
cencomssh.dll
cencom.dll

Rename the existing copies of the two DLL files in your TinyTERM install directory as backups. Next, copy in the new versions and the batch file. Once that’s done, run the batch file from the TinyTERM directory. This will register the files and should take care of the printing problem.

CR 244, fixed in TinyTERM Plus 4.21

Any network connection requires a TCP port be open and available on the server. There is an excellent list of common TCP ports at www.iss.net.

If you are using a non-standard port in TERM, you can specify the correct port by adding to the address, after a colon. For example:

term -l telnet:192.168.0.1:1023

will cause TERM to use telnet to connect to port 1023, rather than using the default port of 23. TinyTERM for DOS can also be configured this way.

In TinyTERM for Windows, you will need to go into the advanced setup for the telnet, SSH or SSL/TLS protocol. That dialog box will include a port number that can be edited.

At this writing, no file transfer protocol has this capability. This includes FTP in the emulator, as well as the protocols available in the Century FTP Client or SecureFT. The NFS client and server likewise cannot be changed.

CR 235, Century FTP Client
CR 620, FTP in emulator
CR 828, SecureFT

In TinyTERM 4.10 and 4.11, connecting via SSH requires you to save your username and password in the Session Properties. That is a potential security risk. It can be avoided by using this script. It will prompt for a username and password when connecting.

1. You must use the connect button on the ribbon bar when connecting. Auto connect will not work with this script.
2. Save the sshlogin.cs script to the C:\Program Files\Century\TinyTERM directory.
3. Open TinyTERM and click the Session button on the Ribbon Bar, or from the Edit menu select Session Properties.
4. Select the radio button labeled Post session start and click the Browse button below. Browse to the sshlogin.cs script in the TinyTERM directory.
5. Select OK.
6. On the Login tab, clear the username and password if they are saved there.
7. Save the changes and exit Session Properties.

The next time you open TinyTERM and connect with this configuration, you will be prompted for a username and password.

CR 86, prompt added in TinyTERM Plus 4.12
CR 96, sshlogin.cs fails to connect at times

Telnet and SSH servers can automatically detect the terminal type at connection. However, most systems don’t have separate definitions for VT220-7 or VT320-7 emulations. You can correct that with the Telnet terminal type option. Set it to VT220 or VT320 as appropriate, and the host system will recognize the emulation.

TinyTERM Plus 4.10 and higher include the SSH connection type. TinyTERM 4.1x includes only SSH1. Version 4.20 and higher include SSH2 as well. An option to specify SSH2 only at connection was added in TinyTERM Plus 4.31. Public key authentication was added in TinyTERM Plus 4.42.

For help in configuring SSH connections, you can watch screencasts on configuring password authentication and configuring RSA authentication.

In TinyTERM 4.10, the SSH option is grayed out by default. This is due to export restrictions at the time Century Software, Inc., first released the product. You can add SSH by downloading and applying this patch. Download it to a temporary directory, then run it after TinyTERM Plus Edition is installed. It will also work for TinyTERM Thin Client Edition or TinyTERM Web Server Edition version 4.10.

If you have version 4.11 or higher and SSH is grayed out, you have TinyTERM, not TinyTERM Plus. TinyTERM does not include SSH, though TinyTERM Thin Client and TinyTERM Web Server do.

SSH2 is also available in TERM for SCO UNIX and TERM for Linux version 6.28 as a command-line option. The basic command is:

term -lssh:username@host.or.IP

Replace “username” with an actual username, and “host.or.IP” with the correct hostname or IP address.

Century Software, Inc., does not provide SSH daemons for host systems. Check sites such as www.openssh.com for daemons and source code.

CR 37, SSH
CR 144, SSH2
CR 205, RSA key authentication
CR 297, TERM 6.28
CR 481, SSH2 only