<?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: Has SPL-37637 been resolved? in Security</title>
    <link>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40803#M1362</link>
    <description>&lt;P&gt;Support has told me that the bug indeed has been fixed in 4.3&lt;/P&gt;</description>
    <pubDate>Tue, 17 Apr 2012 07:16:10 GMT</pubDate>
    <dc:creator>echalex</dc:creator>
    <dc:date>2012-04-17T07:16:10Z</dc:date>
    <item>
      <title>Has SPL-37637 been resolved?</title>
      <link>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40800#M1359</link>
      <description>&lt;P&gt;I would like to require that our forwarders use SSL.  I've seen references to a bug in 4.2.4 that will break when that setting in exists in inputs.conf.  Has in been resolved in 4.2.5?  I've searched the site for release notes that detail the bugs fixed in the release, but couldn't find anything.&lt;/P&gt;

&lt;P&gt;Thx.&lt;/P&gt;

&lt;P&gt;Craig&lt;/P&gt;</description>
      <pubDate>Tue, 27 Dec 2011 22:18:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40800#M1359</guid>
      <dc:creator>mundus</dc:creator>
      <dc:date>2011-12-27T22:18:12Z</dc:date>
    </item>
    <item>
      <title>Re: Has SPL-37637 been resolved?</title>
      <link>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40801#M1360</link>
      <description>&lt;P&gt;This bug does not prevent the use of SSL. Detailed steps to do so are &lt;A href="http://splunk-base.splunk.com//answers/7164/how-do-i-set-up-ssl-forwarding-with-new-self-signed-certificates-and-authentication"&gt;here&lt;/A&gt;, though the standard docs are also correct. This bug prevents validation of certificates on the &lt;STRONG&gt;client&lt;/STRONG&gt;, i.e., forwarder by the indexer. This is not common.&lt;/P&gt;

&lt;P&gt;However, the bug is not fixed in 4.2.5, but should be fixed in 4.3, which is due out imminently.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Dec 2011 23:35:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40801#M1360</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-12-27T23:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: Has SPL-37637 been resolved?</title>
      <link>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40802#M1361</link>
      <description>&lt;P&gt;We've got some pretty stringent security requirements and don't want a malicious client to interject bad data into the system.&lt;/P&gt;

&lt;P&gt;Thx.&lt;/P&gt;

&lt;P&gt;C&lt;/P&gt;</description>
      <pubDate>Tue, 27 Dec 2011 23:37:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40802#M1361</guid>
      <dc:creator>mundus</dc:creator>
      <dc:date>2011-12-27T23:37:36Z</dc:date>
    </item>
    <item>
      <title>Re: Has SPL-37637 been resolved?</title>
      <link>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40803#M1362</link>
      <description>&lt;P&gt;Support has told me that the bug indeed has been fixed in 4.3&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2012 07:16:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Has-SPL-37637-been-resolved/m-p/40803#M1362</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2012-04-17T07:16:10Z</dc:date>
    </item>
  </channel>
</rss>

