Verify the signature on RPM-based systems Published on Sep 13, 2026
Print
Copy page Copy as Markdown for LLMs View as Markdown View the page as plain text
Open in ChatGPT Ask ChatGPT about this page Open in Claude Ask Claude about this page Prev Next Before installing the software, verify the software authenticity by validating the signature.
Log on to the system as a user with administrator rights.
Locate the public key (GPG) from the software download site.
Import your public key to your RPM DB using this command.
rpm --import <Public_Key_Name>
If you don't import the public key using this command, you will get the following warning message during the installation.
/tmp/tmp.FdcQqEpF3i/McAfeeFW-<vesion_number>-<build_number>.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID <key_number>: NOKEY
Verify the signature.
rpm -K McAfeeESP-<version_number>-<build_number>_x86_64.rpm
rpm -K McAfeeRt-<version_number>-<build_number>_x86_64.rpm
rpm -K McAfeeFW-<version_number>-<build_number>_x86_64.rpm
You get a message similar to McAfeeESP-<version_number>-<build_number>.x86_64.rpm: rsa sha1 (md5) pgp md5 OK
Was this article helpful?
Yes No
Related articles
Endpoint Security (ENS) > ENS 26.x > Trellix Endpoint Security (ENS) 26.x - Installation Guide - Linux > Install software on standalone Linux systems > Install Threat prevention module on standalone systems
Endpoint Security (ENS) > ENS 26.x > Trellix Endpoint Security (ENS) 26.x - Installation Guide - Linux > Install software on standalone Linux systems > Install Firewall module on standalone systems
Endpoint Security (ENS) > ENS 26.x > Trellix Endpoint Security (ENS) 26.x - Installation Guide - Linux > Install software on standalone Linux systems > Install Threat prevention module on standalone systems