<?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: Security audit finds ssl v2 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Security-audit-finds-ssl-v2/m-p/137946#M28375</link>
    <description>&lt;P&gt;By the way, there is no handshake established when port 8089 is chosen, but I am trying to disable ssl v2 on a listening port for this indexer.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jul 2014 21:12:33 GMT</pubDate>
    <dc:creator>ben_leung</dc:creator>
    <dc:date>2014-07-10T21:12:33Z</dc:date>
    <item>
      <title>Security audit finds ssl v2</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Security-audit-finds-ssl-v2/m-p/137945#M28374</link>
      <description>&lt;P&gt;openssl s_client -connect xx.xxx.xx.xx:9998 -ssl2&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Added stanzas to indexer: 
path: etc/system/local/web.conf 
supportSSLV3Only = true 
path: etc/system/local/server.conf 
supportSSLV3Only = true 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What else do I need to stop the use of SSL version 2?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2014 20:21:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Security-audit-finds-ssl-v2/m-p/137945#M28374</guid>
      <dc:creator>ben_leung</dc:creator>
      <dc:date>2014-07-10T20:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: Security audit finds ssl v2</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Security-audit-finds-ssl-v2/m-p/137946#M28375</link>
      <description>&lt;P&gt;By the way, there is no handshake established when port 8089 is chosen, but I am trying to disable ssl v2 on a listening port for this indexer.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2014 21:12:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Security-audit-finds-ssl-v2/m-p/137946#M28375</guid>
      <dc:creator>ben_leung</dc:creator>
      <dc:date>2014-07-10T21:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: Security audit finds ssl v2</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Security-audit-finds-ssl-v2/m-p/137947#M28376</link>
      <description>&lt;P&gt;You can also use supportSSLV3Only in your &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.2/admin/inputsconf"&gt;inputs.conf&lt;/A&gt; in the [SSL] stanza. Maybe go ahead and set some more secure ciphers while you're at it, something like:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[SSL]&lt;BR /&gt;
supportSSLV3Only = true&lt;BR /&gt;
cipherSuite = HIGH&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;However, keep in mind that if you're allowing connections from untrusted networks, you'll probably want to use forwarder to indexer authentication to protect your forwarders from connecting to a rogue indexer. There's pretty good information about how to do this in the &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.2/Security/Aboutsecuringdatafromforwarders"&gt;About securing data from forwarders&lt;/A&gt; section of the documentation but it could add a lot of complexity to your environment. Good luck!&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jul 2014 00:03:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Security-audit-finds-ssl-v2/m-p/137947#M28376</guid>
      <dc:creator>jtacy</dc:creator>
      <dc:date>2014-07-11T00:03:44Z</dc:date>
    </item>
  </channel>
</rss>

