<?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: Root behaviour changed after using modprpw - k root in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140983#M738733</link>
    <description>If you don't see "/tcb" then you aren't in trusted mode anymore.... that could change the behavior.... which in standard/shadow is driven with /etc/default/security AUTH_MAXTRIES (and if SMSE is installed... you can set per-user values with userdbset)&lt;BR /&gt;&lt;BR /&gt;If you still are in trusted ... use getprdef and get /usr/lbin/getprpw to check the settings for the variable umaxlntr&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 07 Feb 2008 00:21:36 GMT</pubDate>
    <dc:creator>Robert Fritz</dc:creator>
    <dc:date>2008-02-07T00:21:36Z</dc:date>
    <item>
      <title>Root behaviour changed after using modprpw - k root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140980#M738730</link>
      <description>Basically my root account was locked and i started my hpux server in single user mode and execute this command modprpw - k root and reboot system and access it with old password,but its behaviour is changed now it is not disabling root after 3 wrong attempts and whenever i create new user it does'nt ask to enter password for that user and it assign default password to this user.</description>
      <pubDate>Wed, 06 Feb 2008 07:07:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140980#M738730</guid>
      <dc:creator>Asim Azhar</dc:creator>
      <dc:date>2008-02-06T07:07:38Z</dc:date>
    </item>
    <item>
      <title>Re: Root behaviour changed after using modprpw - k root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140981#M738731</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;You could have a script disabling the root password.&lt;BR /&gt;&lt;BR /&gt;The command you used should have worked.&lt;BR /&gt;&lt;BR /&gt;When I am forced to take a system to single user mode I run a simple passwd command.&lt;BR /&gt;&lt;BR /&gt;Note also that a console root login is supposed to reset a locked root password.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 06 Feb 2008 10:33:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140981#M738731</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-02-06T10:33:12Z</dc:date>
    </item>
    <item>
      <title>Re: Root behaviour changed after using modprpw - k root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140982#M738732</link>
      <description>run /usr/lbin/getprpw root&lt;BR /&gt;the last field will be the lockout code/reason with an unlocked account = to all zeros e.g.:&lt;BR /&gt;&lt;BR /&gt;lockout=0000000&lt;BR /&gt;&lt;BR /&gt;If any position 1-7 is = to 1, the account will was locked for the following reason:&lt;BR /&gt;(man getprpw)&lt;BR /&gt;Position 1 &lt;BR /&gt;past password lifetime&lt;BR /&gt;Position 2 &lt;BR /&gt;past last login time (inactive account)&lt;BR /&gt;Position 3 &lt;BR /&gt;past absolute account lifetime&lt;BR /&gt;Position 4 &lt;BR /&gt;exceeded unsuccessful login attempts&lt;BR /&gt;Position 5 &lt;BR /&gt;password required and a null password&lt;BR /&gt;Position 6 &lt;BR /&gt;admin lock&lt;BR /&gt;Position 7 &lt;BR /&gt;password is a *&lt;BR /&gt;&lt;BR /&gt;This will help you isolate the reason/cause of the locked account, a login to the console should override the lock.&lt;BR /&gt;-Brian&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Feb 2008 22:10:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140982#M738732</guid>
      <dc:creator>Brian A. Scurlock_1</dc:creator>
      <dc:date>2008-02-06T22:10:25Z</dc:date>
    </item>
    <item>
      <title>Re: Root behaviour changed after using modprpw - k root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140983#M738733</link>
      <description>If you don't see "/tcb" then you aren't in trusted mode anymore.... that could change the behavior.... which in standard/shadow is driven with /etc/default/security AUTH_MAXTRIES (and if SMSE is installed... you can set per-user values with userdbset)&lt;BR /&gt;&lt;BR /&gt;If you still are in trusted ... use getprdef and get /usr/lbin/getprpw to check the settings for the variable umaxlntr&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 07 Feb 2008 00:21:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-behaviour-changed-after-using-modprpw-k-root/m-p/4140983#M738733</guid>
      <dc:creator>Robert Fritz</dc:creator>
      <dc:date>2008-02-07T00:21:36Z</dc:date>
    </item>
  </channel>
</rss>

