Interactive Installation on AIX
The AIX typical install is an interactive script that asks you a series of questions during the installation. You can also install CTE using a silent installer which pre-packages the install information. This allows you to install CTE on a large number of hosts. (For more information, see Silent Installation on AIX).
After you install CTE, you are prompted to register it immediately with a key manager. CTE must be registered with a key manager before you can protect any of the devices on the host. However, you may postpone the registration if you plan to register CTE later.
Note
Do not install CTE on network-mounted volumes like NFS.
Before You Begin
The following prerequisites must be met for CTE/CTE-U to install and register to CipherTrust Manager properly:
-
CipherTrust Manager installed and configured. See CipherTrust Manager Documentation for more information.
-
CipherTrust Manager must contain a Client Profile. See Changing the Profile for more information.
-
CipherTrust Manager must contain a registration token. See Creating a Registration Token.
-
Optionally, the name of the host group you want this client to be a part of.
Procedure
-
Log on to the host where you will install the CTE Agent as
root
. You cannot install the CTE Agent without root access. -
Copy or mount the installation file to the host system. If necessary, make the file executable with the
chmod
command. -
Install the CTE Agent. A typical installation uses the following syntax:
For example:
To install the CTE Agent in a custom directory, use the
-d <custom-dir>
option. For example:Note
If possible, Thales recommends that you use the default directory
/opt/vormetric
.To view all installer options, use the
-h
parameter. For example: -
The Thales License Agreement displays. When prompted, type Y and press Enter to accept.
The install script installs the CTE Agent software in either
/opt/vormetric
or your custom installation directory and then prompts you about registering the CTE Agent with a key manager.Welcome to the CipherTrust Transparent Encryption File System Agent Registration Program.
-
Enter Y to continue with the registration process. The install script prompts you to enter the host name or IP address of the CipherTrust Manager with which you want to register CTE.
The default communication port is 443. If you want to specify a different communication port, enter it with the primary key manager host name in the format: <hostName>:<port#>
For example:
-
Enter the client host name when prompted.
-
Enter the CipherTrust Manager registration token, profile name, host group and host description. If you omit the profile name, CipherTrust Manager associates the default client profile with this client.
-
At the hardware association prompt, select whether you want to enable the hardware association feature to prevent cloned machines from accessing the key manager (for details, see Hardware Association (Cloning Prevention) Option). The default is Y (enabled):
It is possible to associate this installation with the hardware of this machine. If selected, the agent will not contact the key manager or use any cryptographic keys if any of this machine's hardware is changed. This can be rectified by running this registration program again. Do you want to enable this functionality? (Y/N) [Y]: Y
Warning
The registration token, profile name, client group name are case-sensitive. If any of these are entered incorrectly, the client registration will not succeed. If the registration fails, click Back in the installer and verify that the case is correct for all entries on this page.
-
CTE finishes the installation and registration process.
-
If you are using CipherTrust Manager version 2.2 or later, you can now use CipherTrust Manager to administer CTE on the client.
If you are using CipherTrust Manager version 2.1 or earlier, change the client password using the manual password creation method. This password allows users to access encrypted data if the client is ever disconnected from the CipherTrust Manager. For details on changing the password, see the CipherTrust Manager documentation.