HP-UX 11.00 Trusted mode problem

[phil cook]

I'm running a V-class server in trusted mode & inexplicably this problem has started occuring. Whenever a user is prompted for a new password due to expiration an error message (password not protected) appears. When I attempt to change any password from root using passwd I get a similar message (Current user has no Protected Password entry). Nothing has been changed recently on this machine to my knowledge & HP are having to think about it. Wondering if anyone else has seen this before?

Any help would be appreciated.

[Paula J Frazer-Campbell]

Hi
This is not the answer but may point you in a direct to try.

http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0x2db2d06ed8c8d4118fef0090279cd0f9!1,00.html

Paula

[Paula J Frazer-Campbell]

Hi
This is not the answer but may point you in a direction to try.

http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0x2db2d06ed8c8d4118fef0090279cd0f9!1,00.html

Paula

[Vincente Fernandes]

Try sam, and see if you get the same error message. If yes then looks like you password protected database got corrupt. you may have to restore "/tcb/auth" and all the respected subdirs underneath from system backup. Before restoring see if it happens for only few users, then you can narrow down the restore.

[phil cook]

Thanks to you all for your suggestions, but the problem has vanished. It would appear that the security database account had in some way become corrupted, at least as regards the root account - but we are still trying to work out how/why.

Regards

[support_5]

Hi all,

I have just started to see the same thing on my system.

As root:
$ useradd andy1234
$ passwd andy1234
Changing password for andy1234
Last successful password change for andy1234: NEVER
Last unsuccessful password change for andy1234: NEVER

Current user has no Protected Password entry.

Hello!!! And to make things worse, no user can log in anymore! not even root!

So I unconvert the system to an UN-trusted system in sam. All of a sudden, everything is okay. The users can log in, and root can change andy1234's passwd.

so I decided to change back to a trusted system (in sam). all is okay: authck -p returns no problems.

but once I have converted it to a trusted system, the problems all come back again! What is causing this?

Any help would be much appreciated!

Thanks.

- Andy Gray

[Anthony Yau]

What is the output of the following command?

/usr/lbin/getprpw [userid]
e.g. /usr/lbin/getprpw root

[support_5]

It's okay, I asked this question in another thread in the end. the solution was to change the entries in /etc/nsswitch.conf for the passwd and group entries from "compat" to "files". This has fixed the problem. Thanks anyway.

- Andy Gray

[Scott Van Kalken]

an easy way to check for these sorts of errors on a trusted system is via the authck command.

running authck -a will check and fix just about everything.