<?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 issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836649#M90299</link>
    <description>What about the dial-in server? How can I see an incoming telnet from its IP address? If somebody perform an action during this telnet session from the dial-in server as root, and is not me - then I still have something. Another question - after modifying /var/adm/inetd.sec do I have to stop-start inetd?</description>
    <pubDate>Thu, 31 Oct 2002 10:17:16 GMT</pubDate>
    <dc:creator>Ionut Grigorescu_2</dc:creator>
    <dc:date>2002-10-31T10:17:16Z</dc:date>
    <item>
      <title>security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836645#M90295</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm administrating some HP-UX 11.00 machines on which is installed some third party software. The vendor need remote access from time to time to install some new change notes or for solving helpdesk request. They need always the root password for that. My system is accessible via a dial-in server (PC). From there telnet is possible to all my machines (about 10 pcs.) Untill now I have changed each time the root passwd before and after they accessed my system. Is there another better method (for example editing /var/adm/inetd.sec). I want also to know if it's possible to log their activity (don't forget they are root! ).&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;BR /&gt;ionu</description>
      <pubDate>Thu, 31 Oct 2002 08:30:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836645#M90295</guid>
      <dc:creator>Ionut Grigorescu_2</dc:creator>
      <dc:date>2002-10-31T08:30:12Z</dc:date>
    </item>
    <item>
      <title>Re: security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836646#M90296</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I would suggest using sudo. With sudo configured, a user can login using his username / password and then use sudo to execute commands with supervisor  priveleges. All commands executed can be logged.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;-balaji</description>
      <pubDate>Thu, 31 Oct 2002 08:43:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836646#M90296</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2002-10-31T08:43:56Z</dc:date>
    </item>
    <item>
      <title>Re: security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836647#M90297</link>
      <description>What is sudo?</description>
      <pubDate>Thu, 31 Oct 2002 09:33:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836647#M90297</guid>
      <dc:creator>Ionut Grigorescu_2</dc:creator>
      <dc:date>2002-10-31T09:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836648#M90298</link>
      <description>Hi Ionu,&lt;BR /&gt;&lt;BR /&gt;You could consider using auditing (for which your system would need to be trusted.)  However if your vendor is logged in as root, you cannot determine their activities from any other user logged in as root.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;&lt;BR /&gt;Darren.</description>
      <pubDate>Thu, 31 Oct 2002 09:51:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836648#M90298</guid>
      <dc:creator>Darren Prior</dc:creator>
      <dc:date>2002-10-31T09:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836649#M90299</link>
      <description>What about the dial-in server? How can I see an incoming telnet from its IP address? If somebody perform an action during this telnet session from the dial-in server as root, and is not me - then I still have something. Another question - after modifying /var/adm/inetd.sec do I have to stop-start inetd?</description>
      <pubDate>Thu, 31 Oct 2002 10:17:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836649#M90299</guid>
      <dc:creator>Ionut Grigorescu_2</dc:creator>
      <dc:date>2002-10-31T10:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836650#M90300</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;You can set up another root lever user creating a seperate home dir and .sh_history file which is then ftped on a min by min basis to a safe machine.&lt;BR /&gt;&lt;BR /&gt;ie.&lt;BR /&gt;roottmp:sqdvvAP3.sZA6:0:3::/use/root-tmp:/sbin/sh &lt;BR /&gt;&lt;BR /&gt;This not perfect but will help.&lt;BR /&gt;&lt;BR /&gt;I would seriously question the root level access requirement and investigate moving their access level to a more normal level either by forcing them to change their software or for you to take control of the root level tasks.&lt;BR /&gt;&lt;BR /&gt;Basicly root is God and one God is more than enough.&lt;BR /&gt;&lt;BR /&gt;Paula</description>
      <pubDate>Thu, 31 Oct 2002 12:35:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836650#M90300</guid>
      <dc:creator>Paula J Frazer-Campbell</dc:creator>
      <dc:date>2002-10-31T12:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836651#M90301</link>
      <description>Find the things like&lt;BR /&gt;1.Is the root privileges really reqd.?&lt;BR /&gt;2.what is the need for the root privileges?&lt;BR /&gt;&lt;BR /&gt;The secure method is to nstall 'sudo'.&lt;BR /&gt;Using sudo you can restrict users to some root privileges.&lt;BR /&gt;&lt;BR /&gt;check this link for more about sudo&lt;BR /&gt;&lt;A href="http://hpux.connect.org.uk/hppd/hpux/Sysadmin/sudo-1.6.6/" target="_blank"&gt;http://hpux.connect.org.uk/hppd/hpux/Sysadmin/sudo-1.6.6/&lt;/A&gt; &lt;BR /&gt;</description>
      <pubDate>Thu, 31 Oct 2002 12:50:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836651#M90301</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-10-31T12:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836652#M90302</link>
      <description>Unfortunately the root privileges are really required - some change notes include also HP patches - I'm not allowed to install HP patches by myself - they have to be first tested by Nokia's (the vendor) Product Line against their software :-). You are right Paula - one God and thousand daemons ... :-))</description>
      <pubDate>Thu, 31 Oct 2002 13:06:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issue/m-p/2836652#M90302</guid>
      <dc:creator>Ionut Grigorescu_2</dc:creator>
      <dc:date>2002-10-31T13:06:55Z</dc:date>
    </item>
  </channel>
</rss>

