Archive
Highlighted

Transport Block Signature

Explorer

I need to transport an index and remount it in a new splunk instance for review. The index has block signing on and Show Source works fine to test integrity on the original splunk instance.

The block signature db is also being transported and included on the new instance exactly as configured on the original. However, the block signature test fails.

All searching activity works perfectly. Only block sign integrity is broken.

Is there a special way I need to work with the block signature db to make this work?

The background here is that a third party needs to review the data and confirm integrity, but can't be given direct access to the original instance. So we have them install Splunk Free and mount up a copy of the index.

E.

Tags (1)
0 Karma
Highlighted

Re: Transport Block Signature

Splunk Employee
Splunk Employee

I believe that the target system must have at minimum the public key of the signer. I am not sure, but I think that the default key, unless otherwise configured, would be found in $SPLUNK_HOME/etc/auth/audit/public.pem.

0 Karma
Highlighted

Re: Transport Block Signature

Explorer

We never could get this to work. Then 4.2 came out and blocksignatures were completely broken.

Hope that changes.

E.

View solution in original post

0 Karma