ICE

After the fall (October 2017) creators update (1709) for Windows 10, the top level installer for Pro shows hieroglyphics in opening screen when presented with the version choosing option.

This has something to do with Microsoft's font caching and isn't likely to be addressed until Spring or Fall of 2018.

You can work around it for now in a couple of different ways.

First, extract the Pro Installer (using 7-zip or another program) onto your desktop (extract to a folder).

Then one of the following:

Click into that folder where Pro was extracted, then right-click on Setup do Properties click on the Compatibility tab, click Run this program in compatibility mode for and select Windows 98/me. Click on Apply, then Ok. That will exit compatibility settings. Now just double-click on Setup in that folder and it should run without hieroglyphics.

or


Click into that folder where Pro was extracted and go into the folder of the component you are trying to install, say the User install files then TCP-Pro and click on the setup for the respective component.

You'll eventually need to go into the Admin Install Files and run the setup in there so you can apply your license.

After playing with this a bit more I've found the minimum necessary additions to the sshd_config for allowing TelnetPro to login for systems that have disabled sha1 by default, the minimum requirement is to have diffie-hellman-group1-sha1 like this:

KexAlgorithms diffie-hellman-group1-sha1

Though you will likely have more like this:
KexAlgorithms diffie-hellman-group1-sha1,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,curve25519-sha256
and for Ciphers, aes192-cbc needs to be added to the default list. On my machine this results in the following line for Ciphers:

Ciphers chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes192-cbc

You can find out what your current ssh servers defaults are by using nmap on a machine that has it. (search for Ciphers in the output):
nmap --script ssh2-enum-algos -sV -p 22 localhostWould work if you have nmap on the server that's running ssh and ssh uses port 22 and listens on localhost. Change to work with your specific setup.

Note that this doesn't seem to work for sshd 7.3. That would require a change in TelnetPro.

Edit: updated the KexAlgorithms line.

The hostname field can't be used for a description.
You could put a description into the profile field by making a new profile named with the desired description and based off of an existing profile you want to use for that particular machine.
About 8 characters will show up there without expanding the field.

Correction on this...
I would like to add a description of what each host name is in our list.  I can't add the description to the host name, because the description becomes part of the host name.  Is there any way that I can add a description?

Is it possible to widen the host list column?  When I launch the program, the host names get cut off.  I can expand the column manually, but I wanted to know if the column width can be set when the program is launched.

Bob,

We have recently applied a security update to our HPUX and RHEL databases to use OpenSSH 7.3. The update disables support for SHA-1. The update is causing all ssh connections from ICETCP Pro to be disallowed. My UNIX admins have made the suggested change below, but that does not work. Is there any plan to update the ICETCP Pro product to support SHA-2? If not is it possible to have JRiver recompile a version of ICETCP Pro for use that will support SHA-2?

I did some debugging on this after getting an OpenSSH 7 system running.
The problem connecting isn't directly related to SHA-2, I have it working now with some changes to the Pro code and the settings from the message above.

Bob,

We have recently applied a security update to our HPUX and RHEL databases to use OpenSSH 7.3. The update disables support for SHA-1. The update is causing all ssh connections from ICETCP Pro to be disallowed. My UNIX admins have made the suggested change below, but that does not work. Is there any plan to update the ICETCP Pro product to support SHA-2? If not is it possible to have JRiver recompile a version of ICETCP Pro for use that will support SHA-2?

With newer versions of sshd (for example version 6.7 included with debian 8 (jessie)) you need to modify the the sshd_config file so sshd supports the ciphers and key exchange methods in Dejawint.

To do this add the following to the end of your sshd_config script and restart sshd

Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour

KexAlgorithms diffie-hellman-group1-sha1


With newer versions of sshd (for example version 6.7 included with debian 8 (jessie)) you need to modify the the sshd_config file so sshd supports the ciphers and key exchange methods in TelnetPro.

To do this add the following to the end of your sshd_config script and restart sshd

Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour

KexAlgorithms diffie-hellman-group1-sha1


I have verified the behavior.
I don't have a time frame for a change at this time.