HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Root behaviour changed after using modprpw - k roo...
Operating System - HP-UX
1826290
Members
4520
Online
109692
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2008 11:07 PM
02-05-2008 11:07 PM
Root behaviour changed after using modprpw - k root
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.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2008 02:33 AM
02-06-2008 02:33 AM
Re: Root behaviour changed after using modprpw - k root
Shalom,
You could have a script disabling the root password.
The command you used should have worked.
When I am forced to take a system to single user mode I run a simple passwd command.
Note also that a console root login is supposed to reset a locked root password.
SEP
You could have a script disabling the root password.
The command you used should have worked.
When I am forced to take a system to single user mode I run a simple passwd command.
Note also that a console root login is supposed to reset a locked root password.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2008 02:10 PM
02-06-2008 02:10 PM
Re: Root behaviour changed after using modprpw - k root
run /usr/lbin/getprpw root
the last field will be the lockout code/reason with an unlocked account = to all zeros e.g.:
lockout=0000000
If any position 1-7 is = to 1, the account will was locked for the following reason:
(man getprpw)
Position 1
past password lifetime
Position 2
past last login time (inactive account)
Position 3
past absolute account lifetime
Position 4
exceeded unsuccessful login attempts
Position 5
password required and a null password
Position 6
admin lock
Position 7
password is a *
This will help you isolate the reason/cause of the locked account, a login to the console should override the lock.
-Brian
the last field will be the lockout code/reason with an unlocked account = to all zeros e.g.:
lockout=0000000
If any position 1-7 is = to 1, the account will was locked for the following reason:
(man getprpw)
Position 1
past password lifetime
Position 2
past last login time (inactive account)
Position 3
past absolute account lifetime
Position 4
exceeded unsuccessful login attempts
Position 5
password required and a null password
Position 6
admin lock
Position 7
password is a *
This will help you isolate the reason/cause of the locked account, a login to the console should override the lock.
-Brian
You can do anything you set your mind to when you have vision, determination, and an endless supply of expendable labor.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2008 04:21 PM
02-06-2008 04:21 PM
Re: Root behaviour changed after using modprpw - k root
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)
If you still are in trusted ... use getprdef and get /usr/lbin/getprpw to check the settings for the variable umaxlntr
If you still are in trusted ... use getprdef and get /usr/lbin/getprpw to check the settings for the variable umaxlntr
Those Who Would Sacrifice Liberty for Security Deserve Neither." - Benjamin Franklin
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP