Splunk® Universal Forwarder

Splunk Remote Upgrader for Linux Universal Forwarders

Signature validation for upgrading

Download the forwarder's signature file

Based on Splunk naming conventions, the signature filename should be the <UF package name>.sig. For example, if the universal forwarder package name is splunkforwarder-9.3.2-d8bb32809498-Linux-x86_64.tgz, then the signature filename should be splunkforwarder-9.3.2-d8bb32809498-Linux-x86_64.tgz.sig. The Remote Upgrader for Linux Universal Forwarders will find the universal forwarder package first, and then get the signature filename based on this naming rule.

With the universal forwarder package and signature file, the Remote Upgrader for Linux Universal Forwarders performs validation.

Note the following:

  • Signature validation is mandatory for all package types RPM/DEB/TGZ.
  • Only the universal forwarder version 9.0 and later are signed.
Last modified on 24 January, 2025
Uninstall the Remote Upgrader for Linux Universal Forwarders   Remotely upgrade your universal forwarders

This documentation applies to the following versions of Splunk® Universal Forwarder: 1.0.0, 8.2.11, 8.2.12, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.3.0, 9.3.1, 9.3.2, 9.4.0


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters