Trusted Mode Password Expiration

[Skip Ford]

I'm testing Trusted Mode operation on my test server. I convert via sam. I then run /usr/lbin/modprpw -V to prevent user passwords from expiring. When I tried to login via another user the old password didn't work. I also tried logging in as root and that didn't work.
I have all the latest patches for Trusted Mode operation.
Any ideas??

[Jeff Schussele]

Hi Skip,

When the system converts it will *only* convert the first 8 chars of any PW.

If you then enter the old PW - let's say it was 10 chars - it will evaluate all 10 & it will fail to match.

So enter *only* the first 8 chars & that should match. Then you should probably enter a new 8 char PW.

HTH,
Jeff

[Skip Ford]

One more thing. When I tried to change the user's password as root while in Trusted Mode, I received, in addition to the last login info; the following message:

"Current user has no protected password entry"

[Skip Ford]

The password for the user is only 6 characters.

[Jeff Schussele]

OK - check /tcb/files/auth/?/username entry for that user & see if the PW field is populated.

You may want to convert back
/usr/lbin/tsconvert -r
set new PWs & convert once again.

You could also run authck to verify the TCB integity.
Are you up to date on patches?

Rgds,
Jeff

[Skip Ford]

Jeff:

I checked /tcb/files/auth/?/username and everything looked ok.

I think I'm up to date. I have PHCO_28176 and PHCO_27011 installed which I'm told are the latest.

I'll try changing passwords then try converting again.

I'll then try authck and see what happens.

Thanks and I'll get back.

[Skip Ford]

I changed the user's password, converted to trusted mode. I then ran authck -a and received messages indicating that pts/tXX in Terminal Control database refers to a non-existent terminal, where XX are terminal numbers. I then tried to login as the user to no avail.

[Skip Ford]

This gets better. I converted to trusted, added a new user, tried to login as that user to no avail, I then tried to change the password for the user as root and received the same message indicating the user had no Protected Password entry.