Getting Data In

Is crcSalt = still supported?

ontai
Explorer

I'm trying to index Nessus and Snort rules for use in cross-correlation of security events. In previous versions of Splunk, I had to add an entry in props.conf (crcSalt = ) to ensure that Splunk would reindex the entire file any time the contents changed.

But now when I startup Splunk running 4.3.1, I get errors about a potential syntax error:

Possible typo in stanza [nessus_plugins] in /opt/splunk/etc/apps/ResponsysSecurityConsole/local/props.conf, line 5: crcSalt =

Is this option still supported? If not, what can I do to ensure that Splunk always indexes the complete file when any changes to it are detected?

Thx.

Craig

Tags (2)
0 Karma
1 Solution

sdaniels
Splunk Employee
Splunk Employee

Should be fine. I believe it's crcSalt = <SOURCE>. Needs to be capitilized. And you would put it in inputs.conf.

View solution in original post

sdaniels
Splunk Employee
Splunk Employee

Should be fine. I believe it's crcSalt = <SOURCE>. Needs to be capitilized. And you would put it in inputs.conf.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...