Operating System - HP-UX
1833268 Members
2908 Online
110051 Solutions
New Discussion

Re: root account locked out after trusted system setup

 
mark ferency
New Member

root account locked out after trusted system setup

after setting my hpux 11i system to a trusted system all the accounts including the root account get "login incorrect wait for login retry". i am thinking i will have to boot to single user and modify the /etc/nsswitch.conf and change passwdcompat to passwdfiles. is this correct?
4 REPLIES 4
OldSchool
Honored Contributor

Re: root account locked out after trusted system setup

the original password wasn't longer than 8 characters was it? If so, on an untrusted system, anything after 8 was silently ignored, and the conversion to trusted will only use the first 8
Bill Hassell
Honored Contributor

Re: root account locked out after trusted system setup

If you did not use sam to conver to Trusted, then it is absolutely normal for all accounts to be expired. The undocumented tsconvert command is located in /usr/lbin, the OS backend directory. Commands in that directory are not normally documented and are used by other commands (like sam). tsconvert will always expire *all* accounts after conversion. That's why sam runs the command modprpw -V.

So to fix the problem, you should be able to login using the real console (GSP, not a telnet connection to the OS LAN cards). As mentioned, Trusted systems count every character in a password while standard systems just ignore characters beyond 8 in the password.


Bill Hassell, sysadmin
whiteknight
Honored Contributor

Re: root account locked out after trusted system setup

Mark,

I would suggest you go through the setup trusted system documents before you do it in your production server

http://docs.hp.com/en/B2355-90950/ch08s08.html

hope this help

WK
Problem never ends, you must know how to fix it
Jeeshan
Honored Contributor

Re: root account locked out after trusted system setup

Hi mark

>> am thinking i will have to boot to single user and modify the /etc/nsswitch.conf and change passwdcompat to passwdfiles

Yes, you can proceed.
a warrior never quits