Silent Installation for CTE or CTE-U on Linux

This section describes how to perform a silent (unattended) installation on CTE or CTE-U on a single host. The silent installation automates the installation process by storing the answers to installation and registration questions in a separate file that you create. It installs CTE/CTE-U on the host, and registers the host with the CipherTrust Manager you specify in the silent installation file. You can also use the silent installation to install CTE/CTE-U, on multiple hosts simultaneously.

Prerequisites

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

1. Log on as an administrator to the host where you will install CTE/CTE-U.

2. Create a parameter file and store it on your system, or copy an existing file from another location. The file can contain any of the following parameters:

Example 1: Registering with CipherTrust Manager

The following example contains just the required information for registration with CipherTrust Manager. In this case, the client will be registered with the CipherTrust Manager using its IP address instead of its host name:

SERVER_HOSTNAME=Key-Mgmt-Server.example.com
REG_TOKEN=12345
AGENT_HOST_NAME=10.192.80.86

Example 2: Registering with CipherTrust Manager

The following example specifies the required registration information, adds a host name and description, enables hardware association, and CTE-LDT. In this case, the client will be registered with the CipherTrust Manager using its host name instead of the IP address:

SERVER_HOSTNAME=Key-Mgmt-Server.example.com
REG_TOKEN=12345
AGENT_HOST_NAME=myagent.example.com
HOST_DESC="West Coast Server 12"
USEHWSIG=1
CERT_FIELD_PARAM="/C=US/ST=California/L=San Jose/O=Thales eSecurity/OU=Vormetrics/CN=localhost/emailAddress=admin@thalegroup.com"
SUBJECT_ALT_NAME_PARAM="DNS:www.thalesgroup.com,email:admin@thalesgroup.com"

1. Copy or mount the installation file to the host system. The installation file is in the format:

   CTE

   vee-fs-<release>-<build>-<system>.bin

   Copy

   CTE-U

   cte-fuse_<version>.<build>_<processor>.rpm

   Copy

2. Run the installer using the following syntax:

   CTE

   ./vee-fs-<release>-<build>-<system>.bin [-d <custom-dir>] -s <install-file>

   Copy

   where:

   • -d <custom-dir> is an optional parameter that specifies the installation directory for CTE. If you omit this parameter, CTE is installed in: /opt/vormetric/DataSecurityExpert/agent/

   • -s <install-file> indicates that you want to install CTE silently using the installation options file <install-file>

   For example, if the installation options file is called /tmp/unattended.txt, you would enter:

   ./vee-fs-7.7.0-87-rh8-x86_64.bin -s /tmp/unattended.txt

   Copy

   CTE-U

   rpm -i cte-fuse_<version>.<build>_<processor>.rpm

   Copy

   • Invoke Registration for CTE-U:

     /opt/vormetric/DataSecurityExpert/agent/vmd/bin/register_host silent <silent_reg_file>

     Copy

   

   Note

   You can also invoke registration by replacing 'register_host' with the following two options:

   • REG_HOST_CLEAN: Register and remove certificates used for communication
   • REG_HOST_SILENT_<fileName>: Use silent/non-interactive mode; get name=value input from

3. Verify the installation by checking the CTE/CTE-U processes on the host:

   • Run vmd -v to check that the version of CTE/CTE-U matches that just installed.

   • Run vmsec status to display CTE kernel status. (CTE only)

   • Look at the log files in /var/log/vormetric, especially install.fs.log.<date> and vorvmd_root.log.

4. In CipherTrust Manager, 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.