<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Running a vulnerability scan on my CentOS 6 Splunk forwarder, why am I getting &amp;quot;Deprecated SSLv2 and SSLv3 Protocol Detection: port 8089&amp;quot;? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Running-a-vulnerability-scan-on-my-CentOS-6-Splunk-forwarder-why/m-p/208790#M41129</link>
    <description>&lt;P&gt;This fixed it, thanks.&lt;/P&gt;

&lt;P&gt;As an aside I realised a quicker way of testing it is to use the openssl connect&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; openssl s_client -connect localhost:8089 -ssl2
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 10 Sep 2015 14:02:12 GMT</pubDate>
    <dc:creator>terryjohn</dc:creator>
    <dc:date>2015-09-10T14:02:12Z</dc:date>
    <item>
      <title>Running a vulnerability scan on my CentOS 6 Splunk forwarder, why am I getting "Deprecated SSLv2 and SSLv3 Protocol Detection: port 8089"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Running-a-vulnerability-scan-on-my-CentOS-6-Splunk-forwarder-why/m-p/208788#M41127</link>
      <description>&lt;P&gt;I am running a Centos 6 machine with splunkforwarder-6.2.5 installed. When running a vulnerability scan using OpenVAS, it tells me that usage of SSLv2 and SSLv3 can be detected. The messages are &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Deprecated SSLv2 and SSLv3 Protocol Detection: port 8089
  It was possible to detect the usage of the deprecated SSLv2 and/or SSLv3 protocol on this system.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have edited $SPLUNK_HOME/etc/system/local/inputs.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[SSL]
sslVersions = tls
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have also edited $SPLUNK_HOME/etc/system/local/web.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[settings]
enableSplunkWebSSL = 1
sslVersions = tls
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;After restarting the forwarder, another scan showed the same vulnerabilities. &lt;/P&gt;

&lt;P&gt;I need to know if these are the right files to change to prevent the splunk forwarder from using any protocol less than TLSv1.0&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2015 09:56:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Running-a-vulnerability-scan-on-my-CentOS-6-Splunk-forwarder-why/m-p/208788#M41127</guid>
      <dc:creator>terryjohn</dc:creator>
      <dc:date>2015-09-10T09:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: Running a vulnerability scan on my CentOS 6 Splunk forwarder, why am I getting "Deprecated SSLv2 and SSLv3 Protocol Detection: port 8089"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Running-a-vulnerability-scan-on-my-CentOS-6-Splunk-forwarder-why/m-p/208789#M41128</link>
      <description>&lt;P&gt;The settings you have chosen are for Splunk Web, not the management port (8089). You need to edit the &lt;CODE&gt;server.conf&lt;/CODE&gt;. &lt;/P&gt;

&lt;P&gt;server.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [sslConfig]
 sslVersions = tls
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The documentation is at &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.5/admin/Serverconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.5/admin/Serverconf&lt;/A&gt; . The relevant portion is below.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sslConfig]
* Set SSL for communications on Splunk back-end under this stanza name.
    * NOTE: To set SSL (eg HTTPS) for Splunk Web and the browser, use web.conf.
* Follow this stanza name with any number of the following attribute/value pairs.  
* If you do not specify an entry for each attribute, Splunk will use the default value.

sslVersions = &amp;lt;versions_list&amp;gt;
* Comma-separated list of SSL versions to support
* The versions available are "ssl2", "ssl3", "tls1.0", "tls1.1", and "tls1.2"
* The special version "*" selects all supported versions.  The version "tls"
  selects all versions tls1.0 or newer
* If a version is prefixed with "-" it is removed from the list
* When configured in FIPS mode ssl2 and ssl3 are always disabled regardless of this configuration
* Defaults to "*,-ssl2".  (anything newer than SSLv2)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 10 Sep 2015 11:24:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Running-a-vulnerability-scan-on-my-CentOS-6-Splunk-forwarder-why/m-p/208789#M41128</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2015-09-10T11:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: Running a vulnerability scan on my CentOS 6 Splunk forwarder, why am I getting "Deprecated SSLv2 and SSLv3 Protocol Detection: port 8089"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Running-a-vulnerability-scan-on-my-CentOS-6-Splunk-forwarder-why/m-p/208790#M41129</link>
      <description>&lt;P&gt;This fixed it, thanks.&lt;/P&gt;

&lt;P&gt;As an aside I realised a quicker way of testing it is to use the openssl connect&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; openssl s_client -connect localhost:8089 -ssl2
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 10 Sep 2015 14:02:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Running-a-vulnerability-scan-on-my-CentOS-6-Splunk-forwarder-why/m-p/208790#M41129</guid>
      <dc:creator>terryjohn</dc:creator>
      <dc:date>2015-09-10T14:02:12Z</dc:date>
    </item>
  </channel>
</rss>

