<?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: How should I configure a Splunk instance to run smoothly as a regular Splunk user versus root? in Security</title>
    <link>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240117#M6716</link>
    <description>&lt;P&gt;Another side note, this post from @Gilles &lt;A href="http://unix.stackexchange.com/questions/10735/linux-allowing-an-user-to-listen-to-a-port-below-1024"&gt;http://unix.stackexchange.com/questions/10735/linux-allowing-an-user-to-listen-to-a-port-below-1024&lt;/A&gt; provides three possible solutions for this. From my point of view the docs &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/installation/RunSplunkasadifferentornon-rootuser"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.2/installation/RunSplunkasadifferentornon-rootuser&lt;/A&gt; should be modified in this regard - I'll ping @docs &lt;/P&gt;</description>
    <pubDate>Fri, 22 Jan 2016 00:11:40 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2016-01-22T00:11:40Z</dc:date>
    <item>
      <title>How should I configure a Splunk instance to run smoothly as a regular Splunk user versus root?</title>
      <link>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240112#M6711</link>
      <description>&lt;P&gt;I find that I encountered more problems running splunk instances as the user &lt;CODE&gt;splunk&lt;/CODE&gt; than using &lt;CODE&gt;root&lt;/CODE&gt;. When I use &lt;CODE&gt;splunk&lt;/CODE&gt; to start a Splunk instance, the receiving port that I use to listen to incoming forwarded data could not be started up. When I use &lt;CODE&gt;root&lt;/CODE&gt; to start Splunk instance, then everything works. So, should I be running Splunk instance with &lt;CODE&gt;root&lt;/CODE&gt; or not? If not, how should I configure Splunk instance to run smoothly user a normal user account.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 01:13:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240112#M6711</guid>
      <dc:creator>michael_lee</dc:creator>
      <dc:date>2016-01-21T01:13:05Z</dc:date>
    </item>
    <item>
      <title>Re: How should I configure a Splunk instance to run smoothly as a regular Splunk user versus root?</title>
      <link>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240113#M6712</link>
      <description>&lt;P&gt;Hi michael_lee,&lt;/P&gt;

&lt;P&gt;this is not a Splunk problem, this is based on the so called privileged ports. The TCP/IP port numbers below 1024 are special in that normal users are not allowed to run servers on them. This is a security feature of your OS, in that if you connect to a service on one of these ports you can be fairly sure that you have the real thing, and not a fake which some hacker has put up for you.&lt;/P&gt;

&lt;P&gt;If you want to use the port 800 with Splunk inputs, create a new Splunk tcp input on port 1800 and use a iptables rule to route input for port 800 to the Splunk port 1800:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;   /usr/sbin/iptables -t nat -A PREROUTING -m tcp -p tcp --dport 800 -j REDIRECT --to-ports 1800
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Your Sysadmin can do this for you.&lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 02:15:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240113#M6712</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-01-21T02:15:06Z</dc:date>
    </item>
    <item>
      <title>Re: How should I configure a Splunk instance to run smoothly as a regular Splunk user versus root?</title>
      <link>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240114#M6713</link>
      <description>&lt;P&gt;thanks. so what should be running on port 800? is port 800 in your example a service? &lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 02:33:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240114#M6713</guid>
      <dc:creator>michael_lee</dc:creator>
      <dc:date>2016-01-21T02:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: How should I configure a Splunk instance to run smoothly as a regular Splunk user versus root?</title>
      <link>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240115#M6714</link>
      <description>&lt;P&gt;This is the port Splunk will open for your input and it's just an example, instead of &lt;CODE&gt;foo&lt;/CODE&gt; I used &lt;CODE&gt;800&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 02:37:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240115#M6714</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-01-21T02:37:57Z</dc:date>
    </item>
    <item>
      <title>Re: How should I configure a Splunk instance to run smoothly as a regular Splunk user versus root?</title>
      <link>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240116#M6715</link>
      <description>&lt;P&gt;As a note here, Splunk by default uses ports &amp;gt; 1024, which dont require priv to open. For example the default web port is TCP/8000 and the Default SplunkIn port is TCP/9997.&lt;/P&gt;

&lt;P&gt;In cases where you want to use ports &amp;lt; 1024, you will need root or super user level access to do this.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 04:26:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240116#M6715</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2016-01-21T04:26:55Z</dc:date>
    </item>
    <item>
      <title>Re: How should I configure a Splunk instance to run smoothly as a regular Splunk user versus root?</title>
      <link>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240117#M6716</link>
      <description>&lt;P&gt;Another side note, this post from @Gilles &lt;A href="http://unix.stackexchange.com/questions/10735/linux-allowing-an-user-to-listen-to-a-port-below-1024"&gt;http://unix.stackexchange.com/questions/10735/linux-allowing-an-user-to-listen-to-a-port-below-1024&lt;/A&gt; provides three possible solutions for this. From my point of view the docs &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/installation/RunSplunkasadifferentornon-rootuser"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.2/installation/RunSplunkasadifferentornon-rootuser&lt;/A&gt; should be modified in this regard - I'll ping @docs &lt;/P&gt;</description>
      <pubDate>Fri, 22 Jan 2016 00:11:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-should-I-configure-a-Splunk-instance-to-run-smoothly-as-a/m-p/240117#M6716</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-01-22T00:11:40Z</dc:date>
    </item>
  </channel>
</rss>

