9. SSH Manager

9.1 The SSH Manager Benefits

iTivity manages all of your SSH connections to all the computers and devices connected to the hyperserver.

While iTivity provides SSH connectivity, unlike the typical SSH solution, iTivity provides these distinct benefits:

  • Security: SSH requires an inbound port (port 22 by default) to be open to access a remote server directly. This is a clear security risk as it paves the way for man-in-the-middle attacks as well as direct access by any bad actors (ex-employees, hackers, etc.) who possess a working private key. iTivity operates using outbound ports, eliminating the need to open ports on the firewall. This greatly improves security.

  • Scale: Reverse SSH tunnels are often used to gain access to systems that are behind firewalls so that inbound ports can remain closed. While this approach does work, it does not scale well. A reverse tunnel has to be created on every remote server for every user. Trying to create and maintain tunnels on more than a handful of systems for a very small team becomes very time-consuming and inefficient. And it requires access to the remote server in the first place to set it all up. iTivity automatically creates application tunnels, eliminating the need to spend time and resources creating reverse SSH tunnels to access remote systems. iTivity's application tunnels ensure a persistent and secure connection to each system connected to the hyperserver. These tunnels allow applications, including SSH, to be run on the remote system, even though it resides behind a firewall. The automatic creation and management of application tunnels to a central hyperserver allows the ready scaling of connections to thousands of devices for large teams of users.

  • Access Control: Traditionally, accessing computers via SSH allows one user to connect to one or more computers. As long as that user can authenticate, they can login to the system. The problem is controlling access to systems based on a user’s role or permission status. This becomes particularly problematic when a user leaves the organization or their role changes. With the typical SSH solution, each system would have to be changed to prevent the user from gaining access. This can be extremely time-consuming and impractical. iTivity changes all of that. Since access is centrally controlled through the hyperserver, changing a user’s access is simply a matter of making a change once. This makes securing access to systems faster, easier and more reliable.

  • Persistence: Each SSH tunnel must be managed individually. If a network interruption occurs, it can cause the tunnel to disconnect. This requires manually reconnecting the tunnel. Managing a few tunnels like this is doable; however, it becomes impractical, if not impossible, to maintain as the number of tunnels increases. iTivity eliminates the need to maintain SSH tunnels. iTivity ensures a persistent connection between the agent-connected system and the hyperserver. This means you can be confident that you can access any system as needed without delay or interruption, and without the added overhead of maintaining SSH tunnels.

9.2 The iTivity SSH Client

iTivity provides a Java-based SSH client as a standard feature. The provides for portability of iTivity across a variety of operating environments. The iTivity SSH client is full-featured, providing all standard functionality. It is more efficient as it does not have to provide encryption or tunneling since iTivity provides those functions via its application tunnel. The iTivity SSH client runs as one of the services within this application.

iTivity supports using 3rd-party SSH clients over its application tunnel. See Using a 3rd-Party SSH Client below for more details.

9.3 How to Use the iTivity SSH Manager to Access Remote Systems

To start an SSH session, login to on the hyperserver where the agent system is connected.

Once authenticated, all the agent systems will appear in the main console window.

Single-click on the agent system you wish to select and then click on the SSH option in the console toolbar.

iTivity will automatically start an SSH session and authenticate access to the agent system.

You can launch multiple SSH sessions into the same agent system.

9.4 Using iTivity SSH Manager to Create Tunnels

As stated earlier, iTivity eliminates the need to create SSH tunnels to access systems and their applications. The most common reason SSH tunnels are used is to gain access to systems behind firewalls by tunneling those systems’ network traffic to a local system. Since iTivity puts in place a more reliable, automated, and scalable application tunnel, SSH tunnels are not needed.

The iTivity application tunnel allows a variety of an agent system’s applications to be accessed and run, not just SSH. iTivity recognizes all the common applications including:

  • SSH

  • FTP

  • SFTP

  • HTTP

  • HTTPS

  • RDP

  • VNC

iTivity also recognizes a variety of other applications. You can also configure iTivity to include any custom application that you wish. (See Section 1.5.1 Configuring iTivity AppTunnel for complete details.)

Each application that can be run is automatically displayed in the console. Launching it is simply a matter of double-clicking on it.

9.4.1 Example: Accessing a Web-based Application using iTivity

This example will show how to access the web-based application, phpMyAdmin, using iTivity.

phpMyAdmin is installed and running on a remote system named, agent1, that is behind a firewall. The typical approach to access this application would be to use SSH to create a tunnel from the remote system to the local system (e.g. ssh -p 22800 -l username -t -L 8888:localhost:80 agent1), then launch a browser and access the phpMyAdmin URL on localhost (e.g.https://127.0.0.1:8888/phpmyadmin/index.php)

With iTivity, it is much easier and faster. iTivity automatically discovers applications that are running on agent1. One of these applications are HTTP applications running on port 80. iTivity will display all discovered applications in the console. To access the application, simply point and click on it -- no tunnels to create, authenticate, or maintain.

Select Web Application Automatically Discovered by iTivity

iTivity will then automatically launch phpMyAdmin running on the agent system and display it on the console.

Agent system application running in a secure tunnel on the console.

9.5 Using a 3rd-Party SSH Client

iTivity allows you to use a 3rd-party SSH client instead of the native iTivity SSH client. This will require you to install the 3rd-party SSH client on the system where the console is running and make changes to the iTivity configuration file.

For consoles running on Windows system, this will require you to edit the registry file settings.

To make changes to the registry settings, follow these steps:

1- Save the above contents to a file, say 'ssh.reg'

2- You can use Windows Explorer and just double click on the file above and it will automatically invoke the registry editor and import the settings.

3- OR you can from the PowerShell or any shell issue the command :

regedit ssh.reg

wheressh.reg is in the current directory.

Below are the registry file settings for the many common 3rd-party SSH clients:

9.5.1 PuTTY

The iTivity console can invoke putty.exe as an external emulator using command line options. Below are the registry settings that can be imported into the registry file of the computer running the console.

32-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Tridia\iTivity\Mgr] (32-bit)

"SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068f0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000013880; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="scoansi" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068e0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:0000138860; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="scoansi" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="scoansi" "SSHExternalEmulatorStopServerOnConnect"=dword:000000000; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000060; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000000  "SSHExternalEmulatorPath"="\"C:\Program Files\putty\putty.exe\" -ssh -P 26864 localhost" "DVRCExternalEmulatorPath"="\"C:\Program Files\putty\putty.exe\" -raw -P 26848 localhost" "TelnetExternalEmulatorPath"="\"C:\Program Files\putty\putty.exe\" -telnet -P 26832 localhost" "SSHExternalEmulatorMustUseProxy"=dword:00000000 "DVRCExternalEmulatorMustUseProxy"=dword:00000000 "TelnetExternalEmulatorMustUseProxy"=dword:00000000 ---COPY FROM ABOVE THIS LINE---

64-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Tridia\iTivity\Mgr] (64-bit)

"SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068f0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000013880; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="scoansi" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068e0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:0000138860; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="scoansi" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="scoansi" "SSHExternalEmulatorStopServerOnConnect"=dword:000000000; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000060; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000000  "SSHExternalEmulatorPath"="\"C:\Program Files\putty\putty.exe\" -ssh -P 26864 localhost" "DVRCExternalEmulatorPath"="\"C:\Program Files\putty\putty.exe\" -raw -P 26848 localhost" "TelnetExternalEmulatorPath"="\"C:\Program Files\putty\putty.exe\" -telnet -P 26832 localhost" "SSHExternalEmulatorMustUseProxy"=dword:00000000 "DVRCExternalEmulatorMustUseProxy"=dword:00000000 "TelnetExternalEmulatorMustUseProxy"=dword:00000000 ---COPY FROM ABOVE THIS LINE---

9.5.2 TinyTerm

TinyTerm is invoked as follows: tt.exe -E43 C:\tmp\itivity

TinyTerm will append .tpx to the end of the C:\tmp\itivity so on the agent system a file C:\tmp\itivity.tpx should exist. It is suggested to place this file under the iTivity directory. The reason for the need to use a .tpx file is because that is the only way to communicate to TinyTerm WHERE to connect to. The emulator will go through iTivity localhost:26832 connection. Notice that the port number can be configured, but should not need to be changed.

32-bit System

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Tridia\iTivity\Mgr] (32-bit) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Tridia\iTivity\Mgr] (64-bit) "SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068e0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000007d00; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="vt100" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068e0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:000007d060; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="vt100" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="vt100" "SSHExternalEmulatorStopServerOnConnect"=dword:000000010; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000160; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000001  "SSHExternalEmulatorPath"="\"C:\Program Files\Century\TinyTERM\tt.exe\" -E43 \"C:\tmp\itivity\"" "DVRCExternalEmulatorPath"="\"C:\Program Files\Century\TinyTERM\tt.exe\" -E43 \"C:\tmp\itivity\"" "TelnetExternalEmulatorPath"="\"C:\Program Files\Century\TinyTERM\tt.exe\" -E43 \"C:\tmp\itivity\"" ---COPY FROM ABOVE THIS LINE---

64-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Tridia\iTivity\Mgr] (64-bit) "SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068e0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000007d00; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="vt100" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068e0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:000007d060; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="vt100" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="vt100" "SSHExternalEmulatorStopServerOnConnect"=dword:000000010; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000160; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000001  "SSHExternalEmulatorPath"="\"C:\Program Files\Century\TinyTERM\tt.exe\" -E43 \"C:\tmp\itivity\"" "DVRCExternalEmulatorPath"="\"C:\Program Files\Century\TinyTERM\tt.exe\" -E43 \"C:\tmp\itivity\"" "TelnetExternalEmulatorPath"="\"C:\Program Files\Century\TinyTERM\tt.exe\" -E43 \"C:\tmp\itivity\"" ---COPY FROM ABOVE THIS LINE---

9.5.3 TerraTerm

The registry settings for using TeraTerm Pro are shown below. These assume that TeraTerm Pro is already installed on the target machine and in the path shown in the settings below (the default). If not, just edit the path before applying the registry settings.

32-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Tridia\iTivity\Mgr] (32-bit) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Tridia\iTivity\Mgr] (64-bit) "SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068f0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000013880; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="xterm" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068e0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:0000138860; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="xterm" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="xterm" "SSHExternalEmulatorStopServerOnConnect"=dword:000000000; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000060; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000000  "SSHExternalEmulatorPath"="\"C:\Program Files\teraterm\ttermpro.exe\" 127.0.0.1:26864" "DVRCExternalEmulatorPath"="\"C:\Program Files\teraterm\ttermpro.exe\" 127.0.0.1:26848 /T=1" "TelnetExternalEmulatorPath"="\"C:\Program Files\teraterm\ttermpro.exe\" 127.0.0.1:26832 /T=1" "SSHExternalEmulatorMustUseProxy"=dword:00000000 "TelnetExternalEmulatorMustUseProxy"=dword:00000000 ---COPY FROM ABOVE THIS LINE---

64-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Tridia\iTivity\Mgr] (64-bit) "SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068f0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000013880; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="xterm" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068e0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:0000138860; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="xterm" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="xterm" "SSHExternalEmulatorStopServerOnConnect"=dword:000000000; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000060; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000000  "SSHExternalEmulatorPath"="\"C:\Program Files\teraterm\ttermpro.exe\" 127.0.0.1:26864" "DVRCExternalEmulatorPath"="\"C:\Program Files\teraterm\ttermpro.exe\" 127.0.0.1:26848 /T=1" "TelnetExternalEmulatorPath"="\"C:\Program Files\teraterm\ttermpro.exe\" 127.0.0.1:26832 /T=1" "SSHExternalEmulatorMustUseProxy"=dword:00000000 "TelnetExternalEmulatorMustUseProxy"=dword:00000000 ---COPY FROM ABOVE THIS LINE---

These settings were tested against Tera Term 4.63.

9.5.4 SecureCrt

Below are the registry settings to use for SecureCrt. One assumes that SecureCrt is already installed on the target machine and on the path show in the settings below. If not, just edit the path before applying the registry settings.

32-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Tridia\iTivity\Mgr] (32-bit) [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Tridia\iTivity\Mgr] (64-bit) "SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068f0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000013880; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="scoansi" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068e0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:0000138860; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="scoansi" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="scoansi" "SSHExternalEmulatorStopServerOnConnect"=dword:000000000; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000060; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000000  "SSHExternalEmulatorPath"="\"C:\Program Files\SecureCRT\SecureCRT.exe\" /T /SSH2 127.0.0.1 26864" "DVRCExternalEmulatorPath"="\"C:\Program Files\SecureCRT\SecureCRT.exe\" /T /TELNET 127.0.0.1 26848" "TelnetExternalEmulatorPath"="\"C:\Program Files\SecureCRT\SecureCRT.exe\" /T /TELNET 127.0.0.1 26832" "SSHExternalEmulatorMustUseProxy"=dword:00000000 "TelnetExternalEmulatorMustUseProxy"=dword:00000000 ---COPY FROM ABOVE THIS LINE---

64-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Tridia\iTivity\Mgr] (64-bit) "SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068f0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000013880; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="scoansi" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068e0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:0000138860; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="scoansi" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="scoansi" "SSHExternalEmulatorStopServerOnConnect"=dword:000000000; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000060; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000000  "SSHExternalEmulatorPath"="\"C:\Program Files\SecureCRT\SecureCRT.exe\" /T /SSH2 127.0.0.1 26864" "DVRCExternalEmulatorPath"="\"C:\Program Files\SecureCRT\SecureCRT.exe\" /T /TELNET 127.0.0.1 26848" "TelnetExternalEmulatorPath"="\"C:\Program Files\SecureCRT\SecureCRT.exe\" /T /TELNET 127.0.0.1 26832" "SSHExternalEmulatorMustUseProxy"=dword:00000000 "TelnetExternalEmulatorMustUseProxy"=dword:00000000 ---COPY FROM ABOVE THIS LINE---

9.5.5 PowerTerm

You can configure Power Term to run as the default terminal emulator from your iManager.

Please create/copy two PowerTerm configuration files (text files) on your system.

C:\Program Files\iTivity\bin\ptermconf.pts

C:\Program Files\iTivity\bin\ptermconf.ptc

You can copy a "*.pts" file from the Power Term directory to "ptermconf.pts" or just ask Power Term to save your settings into "ptermconf.pts". However, the "ptermconf.ptc" file must redirect Power Term to use the console supplied connection port. Please refer to these example contents of the "ptermconf.ptc" file:

comm-type = telnet host-name = localhost telnet-port = 26832 set-window-size = true security-type = unsecured terminal-type = vt100 terminal-model = vt100

The following registry settings provide an example configuration using the two files mentioned above.

32-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Tridia\iTivity\Mgr] "SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068d0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000007d00; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="vt100" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068d0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:000007d060; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="vt100" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="vt100" "SSHExternalEmulatorStopServerOnConnect"=dword:000000000; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000060; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000000  "SSHExternalEmulatorPath"="\"C:\Program Files\iTivity\bin\ShellExecuteWait.exe\" \"C:\Program Files\Ericom Software\PowerTerm\ptw32.exe\" \"C:\Program Files\iTivity\bin\ptermconf.pts\"" "DVRCExternalEmulatorPath"="\"C:\Program Files\iTivity\bin\ShellExecuteWait.exe\" \"C:\Program Files\Ericom Software\PowerTerm\ptw32.exe\" \"C:\Program Files\iTivity\bin\ptermconf.pts\"" "TelnetExternalEmulatorPath"="\"C:\Program Files\iTivity\bin\ShellExecuteWait.exe\" \"C:\Program Files\Ericom Software\PowerTerm\ptw32.exe\" \"C:\Program Files\iTivity\bin\ptermconf.pts\"" ---COPY FROM ABOVE THIS LINE---

64-bit Systems

---COPY FROM BELOW THIS LINE--- Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Tridia\iTivity\Mgr] "SSHCanUseExternalTermEmulator"=dword:00000001 "SSHExternalEmulatorPort"=dword:000068d0 "SSHExternalEmulatorStartDelayMilliSecs"=dword:000007d00; "SSHExternalEmulatorOneSession"=dword:00000000 "SSHExternalEmulatorPersonality"="vt100" "DVRCCanUseExternalTermEmulator"=dword:00000001 "DVRCExternalEmulatorPort"=dword:000068d0 "DVRCExternalEmulatorStartDelayMilliSecs"=dword:000007d060; "DVRCExternalEmulatorOneSession"=dword:00000000 "DVRCExternalEmulatorPersonality"="vt100" "TelnetCanUseExternalTermEmulator"=dword:00000001 "TelnetExternalEmulatorPort"=dword:000068d0 "TelnetExternalEmulatorStartDelayMilliSecs"=dword:000007d0  "TelnetExternalEmulatorOneSession"=dword:00000000 "TelnetExternalEmulatorPersonality"="vt100" "SSHExternalEmulatorStopServerOnConnect"=dword:000000000; "DVRCExternalEmulatorStopServerOnConnect"=dword:0000000060; "TelnetExternalEmulatorStopServerOnConnect"=dword:00000000  "SSHExternalEmulatorPath"="\"C:\Program Files\iTivity\bin\ShellExecuteWait.exe\" \"C:\Program Files\Ericom Software\PowerTerm\ptw32.exe\" \"C:\Program Files\iTivity\bin\ptermconf.pts\"" "DVRCExternalEmulatorPath"="\"C:\Program Files\iTivity\bin\ShellExecuteWait.exe\" \"C:\Program Files\Ericom Software\PowerTerm\ptw32.exe\" \"C:\Program Files\iTivity\bin\ptermconf.pts\"" "TelnetExternalEmulatorPath"="\"C:\Program Files\iTivity\bin\ShellExecuteWait.exe\" \"C:\Program Files\Ericom Software\PowerTerm\ptw32.exe\" \"C:\Program Files\iTivity\bin\ptermconf.pts\"" ---COPY FROM ABOVE THIS LINE---

9.6 Using Keys to Authenticate

iTivity supports SSH keys if the SSH client supports them. If you can successfully login to the system with keys using your SSH client independent of iTivity, you will be able to login using keys when your client is configured for use by iTivity.

It is recommended that you test your SSH client connectivity before configuring for use by iTivity.