<?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 How to check status of all SSL certificates in Splunk? in Security</title>
    <link>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163652#M4854</link>
    <description>&lt;P&gt;All,&lt;/P&gt;
&lt;P&gt;To start with, I am not good with SSL issues. Second, I inherited this instance of Splunk with no documentation of any kind so I'm reverse engineering everything.&lt;/P&gt;
&lt;P&gt;That being said, another team in my company sent me the following notice from Hobbit;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;SSL certificate for &lt;A href="https://nn.nn.nn.nn:8000/" target="test_blank"&gt;https://nn.nn.nn.nn:8000/&lt;/A&gt; expires in 9 days

Server certificate:
    subject:/CN=&amp;lt;indexer name&amp;gt;/O=SplunkUser
    start date: 2011-08-09 20:55:35 GMT
    expire date:2014-08-08 20:55:35 GMT
    key size:1024
    issuer:/C=US/ST=CA/L=San Francisco/O=Splunk/CN=SplunkCommonCA/emailAddress=support@splunk.com
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;I don't know how they set this up or where they are getting this information. So I get on the server and follow a procedure that I received from Splunk support a while ago to regenerate certs;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;If you were using the stock certificates, you can regenerate them with this method : 

- to recreate a new splunkweb certificate : 
delete (or move) the files $SPLUNK_HOME/etc/auth/splunkweb/cert.pem and privkey.pem 
and restart splunk 

- to recreate a new splunkd certificate 
delete (or move) the files $SPLUNK_HOME/etc/auth/server.pem 
and restart splunk 
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;I did this but I'm still seeing the Hobbit message. So I run a grep for "[sslConfig]" to see if I can trace down the issue. What I find is this;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;In "etc/system/local/server.conf":
    [sslConfig]
    sslKeysfilePassword = &amp;lt;secret code&amp;gt;

In "var/run/splunk/merged/server.conf":
    [sslConfig]
    caCertFile = cacert.pem
    caPath = $SPLUNK_HOME/etc/auth
    certCreateScript = $SPLUNK_HOME/bin/splunk, createssl, server-cert
    cipherSuite = ALL:!aNULL:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM
    enableSplunkdSSL = true
    sslKeysfile = server.pem
    sslKeysfilePassword = &amp;lt;sceret code&amp;gt;
    supportSSLV3Only = false
    useClientSSLCompression = true
    useSplunkdClientSSLCompression = true
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;I then look at the "$SPLUNK_HOME/etc/auth/cacert.pem" file and see that it is just over 3 years old. But I don't know if this is where my problem is or not.&lt;/P&gt;
&lt;P&gt;What I need to know is how do I check in Splunk what the status is of all my certs, (how old are they etc.) Regenerating what I need will be another issue.&lt;/P&gt;
&lt;P&gt;~Ed&lt;/P&gt;</description>
    <pubDate>Sun, 07 Jun 2020 19:57:48 GMT</pubDate>
    <dc:creator>OldManEd</dc:creator>
    <dc:date>2020-06-07T19:57:48Z</dc:date>
    <item>
      <title>How to check status of all SSL certificates in Splunk?</title>
      <link>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163652#M4854</link>
      <description>&lt;P&gt;All,&lt;/P&gt;
&lt;P&gt;To start with, I am not good with SSL issues. Second, I inherited this instance of Splunk with no documentation of any kind so I'm reverse engineering everything.&lt;/P&gt;
&lt;P&gt;That being said, another team in my company sent me the following notice from Hobbit;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;SSL certificate for &lt;A href="https://nn.nn.nn.nn:8000/" target="test_blank"&gt;https://nn.nn.nn.nn:8000/&lt;/A&gt; expires in 9 days

Server certificate:
    subject:/CN=&amp;lt;indexer name&amp;gt;/O=SplunkUser
    start date: 2011-08-09 20:55:35 GMT
    expire date:2014-08-08 20:55:35 GMT
    key size:1024
    issuer:/C=US/ST=CA/L=San Francisco/O=Splunk/CN=SplunkCommonCA/emailAddress=support@splunk.com
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;I don't know how they set this up or where they are getting this information. So I get on the server and follow a procedure that I received from Splunk support a while ago to regenerate certs;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;If you were using the stock certificates, you can regenerate them with this method : 

- to recreate a new splunkweb certificate : 
delete (or move) the files $SPLUNK_HOME/etc/auth/splunkweb/cert.pem and privkey.pem 
and restart splunk 

- to recreate a new splunkd certificate 
delete (or move) the files $SPLUNK_HOME/etc/auth/server.pem 
and restart splunk 
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;I did this but I'm still seeing the Hobbit message. So I run a grep for "[sslConfig]" to see if I can trace down the issue. What I find is this;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;In "etc/system/local/server.conf":
    [sslConfig]
    sslKeysfilePassword = &amp;lt;secret code&amp;gt;

In "var/run/splunk/merged/server.conf":
    [sslConfig]
    caCertFile = cacert.pem
    caPath = $SPLUNK_HOME/etc/auth
    certCreateScript = $SPLUNK_HOME/bin/splunk, createssl, server-cert
    cipherSuite = ALL:!aNULL:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM
    enableSplunkdSSL = true
    sslKeysfile = server.pem
    sslKeysfilePassword = &amp;lt;sceret code&amp;gt;
    supportSSLV3Only = false
    useClientSSLCompression = true
    useSplunkdClientSSLCompression = true
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;I then look at the "$SPLUNK_HOME/etc/auth/cacert.pem" file and see that it is just over 3 years old. But I don't know if this is where my problem is or not.&lt;/P&gt;
&lt;P&gt;What I need to know is how do I check in Splunk what the status is of all my certs, (how old are they etc.) Regenerating what I need will be another issue.&lt;/P&gt;
&lt;P&gt;~Ed&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jun 2020 19:57:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163652#M4854</guid>
      <dc:creator>OldManEd</dc:creator>
      <dc:date>2020-06-07T19:57:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to check status of all SSL certificates in Splunk?</title>
      <link>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163653#M4855</link>
      <description>&lt;P&gt;I ran the procedure suggested by Splunk support a second time, and it worked.  I don't know why.  I guess I can blame it on Solar Flares.  The message now reads;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SSL certificate for &lt;A href="https://nn.nn.nn.nn:8000/" target="test_blank"&gt;https://nn.nn.nn.nn:8000/&lt;/A&gt; expires in 1095 days

Server certificate:
    subject:/CN=&amp;lt;indexer name&amp;gt;/O=SplunkUser
    start date: 2014-07-31 14:23:43 GMT
    expire date:2017-07-30 14:23:43 GMT
    key size:1024
    issuer:/C=US/ST=CA/L=San Francisco/O=Splunk/CN=SplunkCommonCA/emailAddress=support@splunk.com
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 31 Jul 2014 14:42:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163653#M4855</guid>
      <dc:creator>OldManEd</dc:creator>
      <dc:date>2014-07-31T14:42:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to check status of all SSL certificates in Splunk?</title>
      <link>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163654#M4856</link>
      <description>&lt;P&gt;What procedure/command do you run  to get this output?&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2017 06:54:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163654#M4856</guid>
      <dc:creator>chris</dc:creator>
      <dc:date>2017-10-19T06:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to check status of all SSL certificates in Splunk?</title>
      <link>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163655#M4857</link>
      <description>&lt;P&gt;That output is produced from Hobbit, not Splunk.  Hobbit is a variant of BigBrother.  I just realized the date on your question.  Well I hope this helps anyway.  &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;&lt;A href="http://hobbit.math.cnrs.fr/hobbit/help/about.html"&gt;http://hobbit.math.cnrs.fr/hobbit/help/about.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2020 14:54:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-check-status-of-all-SSL-certificates-in-Splunk/m-p/163655#M4857</guid>
      <dc:creator>dbturner18</dc:creator>
      <dc:date>2020-03-25T14:54:54Z</dc:date>
    </item>
  </channel>
</rss>

