Verifying Package Signatures
This section explains how to verify signatures of the CTE-U installer packages. After the signature is verified, CTE-U can be installed on file servers.
Verifying Signature of rpm Packages
To verify the signature of the rpm package:
-
Download the public key from the Support Portal:
Note
The key is named
610-000250-001_PUBLIC-GPG-CONNECTOR-SIGNING-KEY.key
. -
Save the key on the file server, for example, at /cte/public_key.
-
Navigate to the directory where the extracted CTE-U packages are stored.
-
Import the public key into the rpm keystore, type:
Example
-
Verify the signature, type:
Example
The command output should contain information similar to the following:
If the output contains Signature, key ID
Verifying Signature of deb Packages
To verify the signature of the deb package:
-
Download the public key from the Support Portal:
Note
The key is named
610-000250-001_PUBLIC-GPG-CONNECTOR-SIGNING-KEY.key
. -
Save the key on the file server, for example, at /cte/public_key.
-
Navigate to the directory where the extracted CTE-U packages are stored.
-
Import the public key, type:
For example, run:
-
Verify the signature, type:
If the output contains the text Good signature, the signature is verified successfully.
Verifying Signature of Interactive Installers
To verify the signature of the interactive installer package:
-
Download the public key from the Support Portal:
Note
The key is named
610-000250-001_PUBLIC-GPG-CONNECTOR-SIGNING-KEY.key
. -
Save the key on the file server, for example, at /cte/public_key.
-
Navigate to the directory where the extracted CTE-U packages are stored.
-
Import the public key, type: (The signature cannot be verified without a valid public key.)
For example, run:
-
Verify the signature.
If the output contains a good signature, the signature is verified successfully.