Signed Data Issues with 4.2

Path Finder

Signed index data not showing up correctly with Splunk 4.2. Worked OK on 4.1.

  • Create a new index on indexer (eg. test2_signtest)
  • add in "blockSignSize = 100" to the index's configuration, restart splunk on indexer.
  • configure a new (Splunk 4.2) source to log to indexer, edit inputs.conf and put in "test2_signtest" as index to log to.
  • confirm logging is going on
  • log a bunch of stuff to the new index
  • Look up an entry in indexer search, select "show source"

With 4.1, I would be getting signed data at this point. If it didn't work, then the splunk.log would write out what the problem was. With my new 4.2 setup, I'm getting a "Could not validate this source..." message in the interface instead. While the message recommends reviewing the splunk.log, there's no relevant messages in the splunk.log at all.

So, i'm stuck. Any tips / ideas on how to get signed data with 4.2, or at least entries in the logs so I can troubleshoot whatever issue might be going on?


Tags (1)

Path Finder

Looks like broken block signing is now a known issue with 4.2 GA:

BlockSignature content validation does not work with distributed search. BlockSignature content validation does not work in 4.2 (GA), even without distributed search, and will falsely claim the data has been tampered with. (SPL-38082) (under unsorted)

0 Karma

Path Finder

A quick update, the two systems I updated to 4.2 are no longer reporting their signed data is OK. Reinstalled Splunk on two systems, configured them for block signing and neither are working correctly.

Assuming that block signing is having a problem in 4.2.

0 Karma
State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!