Trusted System and CDE lock

[Martijn Bruns]

Hi, all.

I just tried converting a HP-UX 11 system to Trusted System state.
The problem is that users can't unlock their CDE sessions anymore. Root can't do this either. What's the problem here?

[K.Vijayaragavan.]

Hi,

It happens as the previous password is not acceptable for the system after converting it to a trusted one.

Better to change the password of all the users affected with the problem then they will be able to unlock the CDE screen.

root should be able to login to CDE Login screen's command line login option with the previous password itself.

If you are not able to get the CDE login screen rightnow at your console, if you can reboot the server, then you will be able to do this.

-Vijay

[John Carr_2]

hi

you need to have everyone logged off while you convert to trusted.

login from command line option in CDE.

cp passwd file to passwd.saved
restore backup of /etc/passwd


log everyone out

cp passwd.saved back to passwd

good luck
John.

[K.Vijayaragavan.]

Hi,

At the worst case we can boot the system in single user mode and either convert the system back to untrusted one by issuing the command "tsconvert" or just change the passwords of required users.

-Vijay

[Alex Glennie · Accepted solution]

I think it's because you trusted the system whilst cde was running, use /sbin/init.d/dtlogin stop/start and try again .

I suspect you'd have to untrust the system to allow users to unlock their current sessions too

[Martijn Bruns]

Thanks a lot for the help.

It seems to be sufficient for the users just to log out and log in again after the conversion.

Dtsession is the process that fires the locking mechanism. When you restart this it starts in a Trusted System (mode/version?), even displaying the lastlog-message on login and unlock.

Again, thanks.