<?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 IDs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612429#M376733</link>
    <description>Hey;&lt;BR /&gt;&lt;BR /&gt;man security(4); the option you're looking for is called SU_ROOT_GROUP.  It's effective since 11.11.&lt;BR /&gt;&lt;BR /&gt;So, define a group you want to be able to su - root, then define it in the security file:&lt;BR /&gt;&lt;BR /&gt;groupadd sysadm&lt;BR /&gt;echo "SU_ROOT_GROUP=sysadm" &amp;gt;&amp;gt; /etc/default/security&lt;BR /&gt;&lt;BR /&gt;should do the trick.&lt;BR /&gt;&lt;BR /&gt;Doug O'Leary&lt;BR /&gt;</description>
    <pubDate>Tue, 06 Apr 2010 12:02:55 GMT</pubDate>
    <dc:creator>Doug O'Leary</dc:creator>
    <dc:date>2010-04-06T12:02:55Z</dc:date>
    <item>
      <title>Security IDs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612425#M376729</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;How to create/set an ID that cannot switch user to root?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Feng Lin</description>
      <pubDate>Tue, 06 Apr 2010 05:12:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612425#M376729</guid>
      <dc:creator>Fenglin</dc:creator>
      <dc:date>2010-04-06T05:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: Security IDs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612426#M376730</link>
      <description>Do you assume that the owner(s) of that ID will get to know the root password? If so, you have a critical problem in your root password management: fix that first.&lt;BR /&gt;&lt;BR /&gt;You can create a group that includes all the users that should be allowed to switch to root, then change the permissions of the "su" command to make it executable by that group only.&lt;BR /&gt;&lt;BR /&gt;Restricting the "su" command will make it difficult to access other non-personal user accounts (i.e. application user accounts). So you may have to provide an alternative that allows more flexible security controls than the "su" command. A common alternative is "sudo": it is available in the free HP Internet Express package.&lt;BR /&gt;&lt;BR /&gt;"sudo" allows the sysadmin to define the things a user is allowed to do using accounts other than his/her own, in a case-by-case basis. &lt;BR /&gt;&lt;BR /&gt;When using sudo to switch from ID A to ID B, the user is not normally asked the password of ID B. Instead, if the action is allowed in the sudo configuration, the user may be simply allowed to do it, or required to enter the password of ID A to confirm their identity. If you want sudo to require the password of ID B, that is configurable too.&lt;BR /&gt;&lt;BR /&gt;From a security perspective, it would be best if each user has a unique, personal ID which is used by nobody else. If the user hasn't been authorized to do something, the system should stop him/her from doing it at all. From the ease-of-use perspective, if the user has been authorized to do something, it should "just work" with the minimum required extra steps because of security restrictions. That's exactly the combination of behaviours you can achieve with sudo.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Tue, 06 Apr 2010 06:01:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612426#M376730</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2010-04-06T06:01:18Z</dc:date>
    </item>
    <item>
      <title>Re: Security IDs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612427#M376731</link>
      <description>&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1270537286861+28353475&amp;amp;threadId=87437" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1270537286861+28353475&amp;amp;threadId=87437&lt;/A&gt;</description>
      <pubDate>Tue, 06 Apr 2010 06:03:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612427#M376731</guid>
      <dc:creator>Johnson Punniyalingam</dc:creator>
      <dc:date>2010-04-06T06:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: Security IDs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612428#M376732</link>
      <description>Hi Matti&lt;BR /&gt;&lt;BR /&gt;How do I restrict group A to be able to su to root and group B not to be able to su to root?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Feng Lin</description>
      <pubDate>Tue, 06 Apr 2010 07:29:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612428#M376732</guid>
      <dc:creator>Fenglin</dc:creator>
      <dc:date>2010-04-06T07:29:25Z</dc:date>
    </item>
    <item>
      <title>Re: Security IDs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612429#M376733</link>
      <description>Hey;&lt;BR /&gt;&lt;BR /&gt;man security(4); the option you're looking for is called SU_ROOT_GROUP.  It's effective since 11.11.&lt;BR /&gt;&lt;BR /&gt;So, define a group you want to be able to su - root, then define it in the security file:&lt;BR /&gt;&lt;BR /&gt;groupadd sysadm&lt;BR /&gt;echo "SU_ROOT_GROUP=sysadm" &amp;gt;&amp;gt; /etc/default/security&lt;BR /&gt;&lt;BR /&gt;should do the trick.&lt;BR /&gt;&lt;BR /&gt;Doug O'Leary&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Apr 2010 12:02:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-ids/m-p/4612429#M376733</guid>
      <dc:creator>Doug O'Leary</dc:creator>
      <dc:date>2010-04-06T12:02:55Z</dc:date>
    </item>
  </channel>
</rss>

