8. Linux Agents

iTivity provides a Linux version of the unattended agent for remote support of Linux systems.

This chapter explains how to install, configure and use the unattended agent on Linux.

8.1 Capabilities of the Unattended Agent on Linux

iTivity provides various capabilities for accessing, viewing and remote control of Linux computers. These capabilities are provided by the Linux unattended agent plus additional software.

Base Capabilities

When the unattended agent is installed on a Linux system, you can use the console remotely connect to that system via secure shell login (SSH), TELNET login, remote graphical access to the X-Windows console (VNC), standard and secure web servers (HTTP and HTTPS), file transfer (FTP) and secure file transfer (SFTP). Via the iTivity WebTunnel feature, you can connect to network applications that are accessible to the agent computer.

Additional Capabilites with DoubleVision Pro

If iTivity's DoubleVision Pro software is installed on the Linux system along with the Unattended Agent, then console users can also:

  • List the users (terminal sessions) that are logged in.

  • View the terminal sessions.

Note: DoubleVision Pro is sold separately.

8.2 Installing the Unattended Agent on Linux

Use the following instructions to download and install an Unattended Agent. Filenames and some command names will vary depending on the exact version you are installing.

For information on configuring the unattended agent after installation, see Section 8.4, Configuring the unattended agent on Linux.

1. Go to itivity.net to download the unattended agent Linux distribution file.

Example Filename: linux-agent.tar

Note: Many popular Window's based ZIP file utilities do not properly extract the contents of our distribution files. Please do not attempt to use them with any of the distribution files.

2. Place the downloaded file in your home directory on the Linux server where you want to install the unattended agent.

Example: /home/username/where username is your actual user name

3. Log on as the root user or issue the su command.

4. Change to the /tmp directory.

cd /tmp [Enter]

5. To verify the presence of the distribution file, list the directory contents of your home directory:

ls l /home/username/*.tar [Enter]where username is your actual user name

6. Extract the distribution (*.tar) file:

tar xvf /home/username/<filename>

7. Run the install Unattended Agent script.


8. Files are extracted and the installation completes.

Note: You can start the Unattended Agent from the command line. See Section 8.4, Linux Unattended Agent Commands.

8.3 Configuring the Unattended Agent on Linux

8.3.1 Editing the Agent.conf File

For the Linux version of the Unattended Agent, all configuration settings are controlled by an ASCII text file called agent.conf, which is placed in the /etc/iTivity/ directory on the Linux computer.

You can change the settings by opening the file in any text editor. The following table describes the settings in the file.



Specifies the directory in which the unattended agent is installed. This setting is automatically configured by the Installation program.

Default: /usr/lib/iTivity/iAgent


Specifies the directory where the nattended agent stores information between program invocations. This information includes encryption keys and other data used internally.

Default: /usr/lib/iTivity/iAgent/itivity_data



The agent name and Description as listed in iTivity console for this unattended agent.

The default vnchostname is the Linux machine name. The vnchostdesc can be entered during the Installation procedure.





These settings specify the filenames and location of three files used for encryption. The unattended agent automatically generates default versions of these files the first time it runs. There is no need to change these settings unless the default files in the dataDir directory are not acceptable.






This flag enables or disables verification of the encryption certificate received from the hyperserver.

Enabling this option (setting the value = 1) prevents a change in the encryption certificate on the hyperserver from blocking access.

Caution: Enabling this function prevents iTivity from detecting a man-in-the-middle attack on the encrypted connection.

The recommended practice is to copy the "root.pem" file from your hyperserver to the agent system. For example,

From: Hyperserver System:/usr/lib/iTivity/iServer/itivity_data/root.pem

To: AgentSystem:/usr/lib/iTivity/iAgent/itivity_data/root.pem

When the root.pem file is copied from the hyperserver to the agent system the hyperserver's certificate will be trusted correctly. At this point, autoAcceptAllCerts can remain disabled and providing a higher level of security.

Default: autoAcceptAllCerts=0

Log File Flags

The following options control which events are written to the Syslog. A value of 1 (one) enables logging and a value of 0 (zero) disables logging.

Syslog facility and priority: iTivity.daemon


Arrival of an encrypted connection. Default = 0.


Closing of an encrypted connection. Default = 0.


Agent startup. Default = 1.


Agent shutdown. Default = 1.


Granting of user permission by the agent. Default = 0


Initiation of an SSH session with the agent. Default = 0


Initiation of a TELNET session with the agent. Default = 0


Granting of FTP access by the agent. Default = 0


Granting of Chat access by the agent. Default = 0


Granting of terminal remote control at the agent via DoubleVision Pro. Default = 0

TCP Connection

These settings control the TCP connection ports and interface of the unattended agent.


Must always match proxySvcPort=21800. Default = 21800


The port for hyperserver connections. Default = 23800.


Host DNS for the hyperserver.

Note: You must enter the DNS name for your hyperserver here for the agent to connect.

Default none.

Example: hyperserver.acme_heavy_industries.com



These two settings control the timeout behavior of unattended agent data connections.

transportTimeout - Timeout in milliseconds set for end-to-end or host to host network connections. Keep this value high if using the Internet or other high-latency network transport (such as satellite connections).

serviceTimeout - Timeout in milliseconds for internal or local connections between unattended agent daemons.




Keep-Alive Settings

These three settings control the keep-alive behavior of unattended agent data connections.


Determines whether the unattended agent sends keep alive packets. Not supported on all transports. Values are:

1 (one) - send packets 0 (zero) - no packets.

Default = 1.


In addition, the unattended agent can send application messages to guarantee the connections are viable and detect lost connections more reliably. Set this flag to 1 (enabled) to have the hyperserver verify session status when there is otherwise no network traffic. Values are 1, enabled, and 0, disabled.

Default = 1.


If the iasVerifySessionFlag is set to 1, this value controls how often, in seconds, the verification packets are sent.

Default = 240.




These settings control the reconnect behavior of the unattended agent when the connection to the hyperserver fails. The default is to retry every five minutes for 24 hours and then enter a binary-backoff retry timing. During the binary-back off stage the retry interval is doubled for each failed connection attempt.

connectToIASCycleTime is the cycle time specified in milliseconds between reconnect tries during the first stage of equal intervals. Default = 300000.

connectToIASIntervalRetries is the total number of equal interval retries. Default = 288. The default works out to about 24 hours if the cycle time above is also at default.

connectToIASMaxRetries is the maximum number of retries of any kind. Assign this setting a value of -1 to allow unlimited retries. Default = -1.


Prevents DNS lookups for new connections to query the host name of the foreign system. This can be useful to improve performance in environments with slow DNS service. Values are:

1 (one) - prevent DNS lookup 0 (zero) - allow lookup

Default = 0.


Specifies the list of cipher algorithms to be allowed for incoming connections. If you add other ciphers to the list, it is highly recommended that you keep the default setting as an option. If this unattended agent connects to an hyperserver or is contacted by an console and there is no mutually acceptable cipher algorithm, the connection will fail.

In order for a different cipher to be used, it must also be allowed by the cipherList of the hyperserver. The recommended best practice is to set the same cipherList in all iTivity systems.

Supported OpenSSL ciphers:


Default: cipherList= AES128-SHA:DES-CBC3-SHA

Connector Port Number

These settings provide the ability to control the port number on which the Connector will attempt to find the local service daemons. Local service daemons listen on the localhost interface and provide local, unencrypted access to services.


Remote control authorization and commands. Must always match connectPort=6800

Default = 6800


Unencrypted, raw VNC data

Default = 5900


Telnet daemon

Default = 23


FTP server control port.

Default = 21


FTP server data port (passive mode)

Default = 20


Forwarded hyperserver connections. Must always match transportPort=21800

Default = 21800


This setting provides control over which services the iTivity console user can access on this agent system via iTivity. Each individual service is controlled via a bit flag in this integer. (See the Examples below.)

The console user must first authenticate with the agent system before being allowed to access any services. After authentication (and the authorization check), then the remote user is subject to the permissions restrictions listed in the table. A Status of N/A indicates that this service is Not Available in the Linux unattended agent.

Decimal ValueStatus Description

1 required Command Protocol

2 optional View desktop permission

4 N/A Control desktop permission

8 optional Telnet permission

16 optional FTP permission

32 required Proxy permission

64 N/A Chat permission

128 optional TTY remote control permission

256 optional TTY listing permission

512 N/A RDP permission

1024 N/A desktop sharing

2048 optional dynamic tunnel permission

4096 optional SSH permission

The default is to allow access to all supported iTivity services (after remote user authenticates and passes authorization check).

Default= 65535


For FTP access only, use a value of 1 + 16 = 17, since the command protocol is required and the FTP permission has a value of 16.

For telnet access only, use a value of 1 + 8 = 9.

For TTY Listing and TTY remote control only, use a value of 1 + 128 + 256 = 385


These settings can be used configure the unattended agent to connect to the hyperserver through a proxy server running the HTTP or SOCKS v5 protocol.


One of the following iTivity modes used to define when the agent uses a Proxy Server to connect:

1 Disable. Only connect to hyperserver directly, no proxy server used.

2 - Require. Only connect to hyperserver via proxy, no direct connect.

3 - Fallback. If direct connection fails, then attempt the proxy connection.

4 - Override. If the proxy connection fails, then attempt the direct connection.


DNS name of the Proxy Server


Port used to connect to the Proxy Server


User name used for secure login to the Proxy Server.


Password used for secure login to the Proxy Server.


One of the following iTivity modes used to define when the agent uses a Proxy Server to connect:

1 Disable. Only connect tohyperserver directly, no proxy server used.

2 - Require. Only connect to hyperserver via proxy, no direct connect.

3 - Fallback. If direct connection fails, then attempt the proxy connection.

4 - Override. If the proxy connection fails, then attempt the direct connection.


DNS name of the Proxy Server


Port used to connect to the Proxy Server


User name used for secure login to the Proxy Server.


Password used for secure login to the Proxy Server.


Enables debugging output in the connector daemons. A setting of zero ("0") disables output. As the mode number increases from one ("1") to twelve ("12"), more and more information is written to the log file. This option should be disabled in production systems, unless instructed otherwise by iTivity staff.

Default = 0.




These settings control the authentication required of iTivity console users to view and control the unattended agent system.

The authscheme setting controls the way the unattended agent authenticates. The default setting is passwd, which requires that the remote user have an account in the native /etc/passwd database. The other currently valid setting is "none, which disables authentication at the unattended agent level may be disabled using the none setting. This is useful in environments where the iTivity hyperserver is trusted and its authentication is deemed sufficient. Other authscheme values are reserved for future use.

The permissionGroup specifies the name of the user group with permission to view and access this system via the unattended agent. To grant a user of iTivity console access, simply add the user to this group. To block a user from using the hyperserver, remove their user id from the group. A user in this group must log in with username and password before viewing this system through iTivity console.

Defaults: permissionGroup = iadmauth authscheme = passwd



These flags control whether it is recorded in the syslog each time a user of iTivity console logs on and logs off of the agent system. Setting the flags to 1 (one) enables logging and provides an audit log of authentication. Setting the flags to 0 (zero) disables logging.

Syslog facility and priority: iTivity.authpriv

logonSysLogMask - Log iTivity console user logon (succeed or fail). Default = 1.

logoffSysLogMask - Log console user logoff (disconnect). Default = 1.




These settings specify the TCP network interface and port on which the processor daemon listens for new unattended agent authentication connections. These connections are internal to the unattended agent and generally use localhost.

The connectPort value must always match the value of commandSvcPort.

The connectTimeout value specifies the socket timeout for processor connections in milliseconds.

Caution: iTivity Corp strongly recommends that you do not change these settings.

Defaults: connectPort=6800 connectHost= connectTimeout=45000


A comma separated list of support domain names which are authorized to access this agent system. See the iTivity Deployment Guide, Section 1.3, Advanced Authentication Using Permission Groups and Support Domains for more information.


This flag indicates whether console users are allowed to update the agent settings remotely (via the console user interface).

Default: 1 (enabled)


Enables debugging output in the processor daemon. The default setting of 0 (zero) disables output. As the number increases from 1 to 12, more and more information is written to the log file. This option should be disabled unless instructed otherwise by iTivity staff.

Default: 0 (disabled)


These settings can be used to configure network applications that will be added to the iTivity WebTunnel scan list for this agent. For more information on WebTurnnel, see Section 1.5.1, Configuring iTivity WebTunnel.


Declares services or applications local to the agent that will be scanned by the agent for the purpose of application tunneling using iTivity WebTunnel. You can configure custom TCP network based services or applications specific to your environment.

customAppScan definitions are indexed using a sequential number ordering. You can configure multiple applications as long as you increment the count.

Example: customAppScan_1, customAppScan_2,

Tunneling of a custom application can be disabled by commenting out the service or application customScanApp_X definition in the agent.conf file and re-loading the agent configuration settings.


Declares the TCP port number of the local agent service or application. If the agent detects a daemon or service listening on your custom port, it will report the service or application as accessible to a connected console. The port value should be between 0 and 65536. This is a required setting for an enabled customAppScan definition.


Declares the protocol used by the local agent service or application. Supported protocols include:

http, https, telnet, vnc, rdp

For web applications, the protocol should be either http or https. This is a required setting for an enabled customAppScan definition


Declares the user readable display name of the service or application to be tunneled. The name should have a clear meaning to a console user. This setting is not required but is highly recommended.


Some operating systems have platform specific session labels. This setting should declare the session in which the application or service is running, if any.

Typical session names would include tty0,pts/4,:4ktcp,#7, etc. This setting is optional.


Specifies the path to the default page or landing page for the application. Typically used for web/http applications. This configuration setting is optional.

8.3.2 Changing a Configuration

You can change configuration options without stopping and restarting the unattended agent software. The options can be changed without losing current connections.

To reload the settings of a running unattended agent, run the following script:


8.4 Linux Unattended Agent Commands

Administrators can use the programs explained in this section to display information about the unattended agent and control its operation. These commands can be found in the agent installation directory. By default, the agent installation directory is:



This command stops execution of the unattended agent by stopping all daemons.


This command displays version information for the currently installed unattended agent.


This command installs the scripts that launch the unattended agent at boot time.


This script starts the unattended agent at system startup.


This program removes the unattended agent files from the system.


This program can be used to manually start the unattended agent.


This program can be used to manually stop the unattended agent.

8.5 iTivity Product Support

Product support is available from iTivity by web site or email:

Copyright © 2004 - 2019, iTivity Corporation Copyright and License Information