<?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: UNIX high authorization profiles are restricted to physically secured devices. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929417#M752425</link>
    <description>thanks for the update Doug.&lt;BR /&gt;-balaji</description>
    <pubDate>Wed, 19 Mar 2003 10:17:45 GMT</pubDate>
    <dc:creator>Balaji N</dc:creator>
    <dc:date>2003-03-19T10:17:45Z</dc:date>
    <item>
      <title>UNIX high authorization profiles are restricted to physically secured devices.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929412#M752420</link>
      <description>HOw can you restrict important profiles such as "root" to have direct logon only from the console?&lt;BR /&gt;&lt;BR /&gt;My program states I should examine the "etc/default/login" for the "CONSOLE=/dev/console" entry.  However the system said no such file exists.  Does this mean etc/default/login first needs to be manually created?&lt;BR /&gt;&lt;BR /&gt;I'd appreciate your responses.  thanks and best regards.</description>
      <pubDate>Tue, 18 Mar 2003 07:37:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929412#M752420</guid>
      <dc:creator>Pat Limaco</dc:creator>
      <dc:date>2003-03-18T07:37:29Z</dc:date>
    </item>
    <item>
      <title>Re: UNIX high authorization profiles are restricted to physically secured devices.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929413#M752421</link>
      <description>hi&lt;BR /&gt;creste the securetty file in /etc directory and the terminal entries from which root can login directly.&lt;BR /&gt;&lt;BR /&gt;echo "console" &amp;gt; /etc/securetty.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;now root can login directly only from the console. note that a user can login and then switch to root still.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;-balaji</description>
      <pubDate>Tue, 18 Mar 2003 07:41:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929413#M752421</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-03-18T07:41:57Z</dc:date>
    </item>
    <item>
      <title>Re: UNIX high authorization profiles are restricted to physically secured devices.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929414#M752422</link>
      <description>Thanks alot, that helped me understand things better.  just a follow up, does this mean i have to put the "root console" entry into the etc/securetty file.  =)</description>
      <pubDate>Tue, 18 Mar 2003 07:53:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929414#M752422</guid>
      <dc:creator>Pat Limaco</dc:creator>
      <dc:date>2003-03-18T07:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: UNIX high authorization profiles are restricted to physically secured devices.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929415#M752423</link>
      <description>no. just the terminal names from where root is allowed to login. this file is used only for user root.&lt;BR /&gt;++++snipped from the login man page++++++++&lt;BR /&gt;If the /etc/securetty file is present, login security is in effect.&lt;BR /&gt;      Only user root is allowed to log in successfully on the ttys listed in&lt;BR /&gt;      this file.  Restricted ttys are listed by device name, one per line.&lt;BR /&gt;      Valid tty names are dependent on the installation.  An example is&lt;BR /&gt;&lt;BR /&gt;           console&lt;BR /&gt;           tty01&lt;BR /&gt;           ttya1&lt;BR /&gt;           etc.&lt;BR /&gt;&lt;BR /&gt;      Note that this feature does not inhibit a normal user from using the&lt;BR /&gt;      su command (see su(1)).&lt;BR /&gt;+++++++++++++++++&lt;BR /&gt;&lt;BR /&gt;man login for more info.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;-balaji</description>
      <pubDate>Tue, 18 Mar 2003 07:58:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929415#M752423</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-03-18T07:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: UNIX high authorization profiles are restricted to physically secured devices.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929416#M752424</link>
      <description>Balaji, /etc/default/security entries on newer (11.11 and later, I think) versions of HP-UX can help with the su case.  Quoting from security(4):&lt;BR /&gt;&lt;BR /&gt;SU_ROOT_GROUP&lt;BR /&gt;This parameter defines the root group name for the su command.  Refer to su(1).&lt;BR /&gt;&lt;BR /&gt;SU_ROOT_GROUP=group_name&lt;BR /&gt;The root group name is set to the specified symbolic group name.  The su command enforces the restriction that a non-superuser must be a&lt;BR /&gt;member of the specified root group to be allowed to su to root.  This does not alter password checking.&lt;BR /&gt;&lt;BR /&gt;Default value: If this parameter is not defined or if it is commented out, there is no default value.  In this case, a non superuser is allowed to su to root without being bound by root group restrictions.&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Mar 2003 09:41:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929416#M752424</guid>
      <dc:creator>doug hosking</dc:creator>
      <dc:date>2003-03-19T09:41:41Z</dc:date>
    </item>
    <item>
      <title>Re: UNIX high authorization profiles are restricted to physically secured devices.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929417#M752425</link>
      <description>thanks for the update Doug.&lt;BR /&gt;-balaji</description>
      <pubDate>Wed, 19 Mar 2003 10:17:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/unix-high-authorization-profiles-are-restricted-to-physically/m-p/2929417#M752425</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-03-19T10:17:45Z</dc:date>
    </item>
  </channel>
</rss>

