Splunk® Universal Forwarder

Splunk Remote Upgrader for Linux Universal Forwarders

Work with signature validation files for upgrading

Download the forwarder's signature file

To download your signature file, in splunk.com select your forwarder version, click "More" and select "Download x509 Signature".

  • Signature validation is mandatory for all package types (RPM, DEB, and TGZ).
  • Only the universal forwarder version 9.0 and later are signed.

The remote upgrader for Linux universal forwarders performs validation with the universal forwarder package and signature file.

To verify that you have the correct signature file, the signature filename should be the <universal forwarder 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 is:

splunkforwarder-9.3.2-d8bb32809498-Linux-x86_64.tgz.sig. 
Last modified on 01 April, 2025
Start or stop the upgrader daemon   Remotely upgrade your universal forwarders

This documentation applies to the following versions of Splunk® Universal Forwarder: 1.0.0, 1.0.1, 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.1.8, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.2.5, 9.3.0, 9.3.1, 9.3.2, 9.3.3, 9.4.0, 9.4.1


Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

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