Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Linux Package Installation for Linux Distributions

Linux Package Installation for RHEL

search

Please Note:

Linux Package Installation for RHEL

This section describes how to access the Linux RPM installation package so that the CTE Agent installation integrates with the distribution software. To access the Linux RPM file, you can:

  • Extract the RPM file from the CTE Agent install bin file. This is the easiest method, but the files in the package are not signed and therefore cannot be verified. For details, see Installing the Unsigned RPM Package.

  • Download the package from the Yum repository. If you use Yum, the files in the package are signed and the signatures are automatically verified when the package is installed. For details, see Installing the Signed RPM Package with Yum.

  • Manually download the RPM package outside of Yum and manually verify the package signatures. For details, see Installing the Signed RPM Package Manually.

Prerequisites

Note

Before you can download and install the package using the Yum repository, you must contact Thales Support to get the username and password for the package repository on which the package resides.

Installing the Unsigned RPM Package

The CTE installation bin files contain the unsigned native packages. Extract them by running the bin file with the -e flag.

  1. Log on to the host system as root and copy, or mount, the installation file to the host system.

  2. Extract the RPM file using the following command:

    ./vee-fs-<release>-<build>-<distro>-<architecture>.bin -e

    Example

    ./vee-fs-7.8.0.75-rh9-x86_64.bin -e

    Response

    Contents extracted.

  3. Verify that the package extracted correctly:

    ls *rpm

    Example Response

    vee-fs-7.8.0.75-rh9-x86_64.rpm

  4. To start the installation using the RPM file, use the following command:

    rpm -ivh vee-fs-<release>-<build>-<distro>-<architecture>.rpm

  5. Follow the prompts to install and register CTE.

    For details about the installation and registration process, see the appropriate installation procedure.

  6. If you are going to register the system with a CipherTrust Manager, see Configuring CTE for Linux with CipherTrust Manager.

Installing the Signed RPM Package with Yum

To install the latest released version with the yum command:

  1. Create the repository file, /etc/yum.repos.d/Vormetric-VTE.repo, with the following content:

    [vormetric-vte]
releasever=REL_VERSION
name=Vormetric VTE Packages $releasever - $basearch – Source
baseurl=https://USER:PASSWORD@packages.vormetric.com/vte/DIST_VERSION/Latest
gpgkey=https://packages.vormetric.com/pub/PKG-GPG-KEY-vormetric
enabled=1
gpgcheck=1
repo_gpgcheck=1
sslverify=1

    Where:

    • USER:PASSWORD: Username/password obtained from Thales Support

    • DIST_VERSION: RHEL release version directory name. Ex: RH8, RH9

    • REL_VERSION: RHEL release version. Ex: rhel-8, rhel-9

  2. Clean up the Yum cache directory:

    yum clean all

  3. List all available versions of CTE:

    yum list --showduplicates vee-fs

  4. Use Yum to install the CTE binary. For example:

    If the CTE binary name is vee-fs-7.8.0.75-rh9-x86_64, type:

    yum install vee-fs-7.8.0.75-rh9-x86_64

    To install the latest version, type:

    yum install vee-fs

    Note

    The first time you install CTE through Yum, you will be asked to import the GPG key. Make sure that you download this key or the installation will fail. For example:

    vormetric-vte/7Server/signature | 198 B 00:00:00
    Retrieving key from https://packages.vormetric.com/pub/PKG-GPG-KEY-vormetric
    Importing GPG key 0x628536B7:
    Userid : "Vormetric (PKG-GPG-KEY) <support@vormetric.com>"
    Fingerprint: 7cb5 4f55 40d4 1b63 bf91 c896 f00a 13b0 6285 36b7
    From : https://packages.vormetric.com/pub/PKG-GPG-KEY-vormetric
    Is this ok [y/N]: y

  5. Follow the prompts to install and register CTE.

    For details about the installation and registration process, see the appropriate installation procedure.

  6. If you are going to register the system with a CipherTrust Manager, see Configuring CTE for Linux with CipherTrust Manager.

Installing the Signed RPM Package Manually

If you want to manually verify the signed version of the CTE RPM package, you can download the public key from the Thales package repository and manually verify the rpm signature.

  1. Download the rpm file for the latest release, type:

    wget -c --user USER --password PASSWORD https://packages.vormetric.com/vte/DIST_VERSION/Latest/TARGET_RPM_NAME

    Example

    wget -c --user ctetest --password abcdef12345678ab https://packages.vormetric.com/vte/RH9/Latest/vee-fs-7.8.0.75-rh9-x86_64.rpm

    Where:

    • DIST_VERSION: RHEL release version directory name. Ex: RH8, RH9

    • USER/PASSWORD: Username/password obtained from Thales Support

    • TARGET_RPM_NAME: Target rpm filename to download. Ex: vee-fs-7.8.0.75-rh9-x86_64.rpm

  2. Import the public key from the Thales package repository:

    sudo rpm --import https://packages.vormetric.com/pub/PKG-GPG-KEY-vormetric
sudo rpm -qa grep gpg-pub*

    Response

    gpg-pubkey-628536b7-56f9887b    : Imported CTE GPG public key.
gpg-pubkey-fd431d51-4ae0493b

  3. Verify the signature of the package.

    sudo rpm -Kv vee-fs-<release>-<build>-<distro>-<architecture>.rpm

    Example

    sudo rpm -Kv vee-fs-7.8.0.75-rh9-x86_64.rpm

  4. To start the installation using the RPM file, use the following command:

    sudo rpm -ivh vee-fs-<release>-<distro>-x86_64.rpm

  5. Follow the prompts to register CTE.

    For details about the installation and registration process, see the appropriate installation procedure.

  6. If you are going to register the system with a CipherTrust Manager, see Configuring CTE for Linux with CipherTrust Manager.

Installing a previous version

To install a previous version with the YUM command, use the following URL for the baseurl in the file, /etc/yum.repos.d/Vormetric-VTE.repo:

    baseurl=https://USER:PASSWORD@packages.vormetric.com/vte/CTE_VERSION/rhel-$releasever/

To install an previous version manually, use the following URL for the download URL.

    https://packages.vormetric.com/vte/CTE_VERSION/REL_VERSION/TARGET_RPM_NAME

Where:

  • USER/PASSWD: contact Thales Support to obtain the credential

  • TARGET_RPM_NAME: Target rpm filename to download. Ex: vee-fs-7.8.0.75-rh9-x86_64.rpm

  • CTE_VERSION: CTE release version. Ex: 7.7.0

  • REL_VERSION: Distribution version. Ex: rhel-8, rhel-9

Upgrading from RHEL 9.6 to RHEL 10

This section describes an In-place upgrade of an RHEL 9.6 system to RHEL 10 using the RHEL Leapp utility, with the added objective of upgrading CTE in the process.

Note

This procedure only applies to when upgrading RHEL 9.6 to RHEL 10. IT does not apply for any other versions.

Leapp allows you to:

  • Preserve the configuration of your system

  • Reinstall RHEL

  • Retain existing subscription data on the client as long as the system is subscribed to using subscription-manager

Note

The upgrade process may take several hours.

Prerequisites

  • Requires an active RHEL subscription on the source system

  • Backup your data using the recommendations in the upgrade guide

Installation with the Leapp Utility

  1. Check the subscription status, type:

    subscription-manager status

  2. Set the subscription manager release, type:

    subscription-manager release --set 9.6

  3. Open the global configuration file, /etc/dnf/dnf.conf, in a text editor for editing.

  4. Add an exception for updating CTE so that Leapp can ignore the CTE package. This lets you upgrade CTE with the CTE Upgrade on Reboot feature. Add the following line to the end of the file:

    exclude=libnsl2,vee-fs

  5. Install the Leapp tools, type:

    yum install leapp  leapp-repository leapp-upgrade

  6. Update the software, type:

    yum update

  7. Reboot the system.

  8. Enable Upgrade on Reboot using the attached schedule.sh file, type:

    ./schedule.sh <cte-binary>

    Example

    ./schedule.sh vee-fs-7.8.0-100-rh10-x86_64.bin

    Note

    The Leapp utility installs the latest CVE kernel package on the target RHEL 10 system. Ensure that the CTE binary provided to the Upgrade on Request scheduler is certified for this kernel version.

  9. Run the pre-upgrade tool, type:

    leapp preupgrade

  10. Examine the pre-upgrade details in /var/log/leapp/leapp-report.txt. Resolve any error or inhibitor conditions.

  11. Rerun the tool after resolving the conditions to verify that they have been resolved.

  12. Set the upgrade target, type:

    leapp preupgrade --target 10.0

  13. Examine the pre-upgrade details again, in /var/log/leapp/leapp-report.txt. Resolve any error or inhibitor conditions.

  14. Rerun the tool after resolving the conditions to verify that they have been resolved.

  15. Start the upgrade, type:

    leapp upgrade --target 10.0

  16. If a failure occurs due to a package or dependency, Leapp logs the error to the console. Fix the issues and then proceed.

    If there are no error or inhibitor conditions displayed on the console, reboot.

  17. Wait for the system to upgrade and return to the online state. Verify the CTE service status.

On this page