On 11/20/21 3:39 PM, Jon Trulson wrote:
Setuid on /usr/dt/bin/dtsession made no difference.
Yeah - it's trying to use the PAM library to validate your
username/pw, but seems to be failing somewhere along the line. Is
there anything of interest in /var/log/secure* ?
Hi, a fix recently went into master that might explain the
dtsession/dtscreen unlock issue. The relevant PAM config files were not
being properly installed unless you used dtlogin. Ubuntu seems to have
a default fallback that works even without these config files, but I
suspect RHEL does not.
Try adding the following two attached files to /etc/pam.d/, mode 644 and
see if that helps anything.
--
Jon Trulson
"This Unit must survive."
-- M5
auth required pam_unix.so
account required pam_nologin.so
account required pam_unix.so
session required pam_lastlog.so
password required pam_deny.so
auth required pam_unix.so
account required pam_deny.so
session required pam_deny.so
password required pam_deny.so
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
