Well, unless I am wrong, the diff in the message 22 breaks xscreensaver's
default pam settings (i.e. settings written as driver/xscreensaver.pam).
driver/xscreensaver.pam essentially just writes:
-------------------------------------
#%PAM-1.0
auth include system-auth
-------------------------------------
(all others are just white spaces or comment lines), and with this pam
settings, xscreensaver pam authentication says with correct password:
xscreensaver: 18:26:00: pam_start ("xscreensaver", "tasaka1", ...) ==> 0
(Success)
xscreensaver: 18:26:00: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 18:26:00: pam_authenticate (...) ...
xscreensaver: 18:26:00: pam_conversation (ECHO_OFF="Password: ") ...
xscreensaver: 18:26:00: 0: mouse is at 1268,777.
xscreensaver: 18:26:00: 0: creating password dialog ("")
xscreensaver: 18:26:00: grabbing server...
xscreensaver: 18:26:00: 0: ungrabbing mouse (was 0xa9).
xscreensaver: 18:26:00: 0: grabbing mouse on 0x34000d8... GrabSuccess.
xscreensaver: 18:26:00: ungrabbing server.
xscreensaver: 18:26:04: input finished.
xscreensaver: 18:26:04: pam_conversation (...) ==> PAM_SUCCESS
xscreensaver: 18:26:04: pam_authenticate (...) ==> 0 (Success)
xscreensaver: 18:26:04: pam_acct_mgmt (...) ==> 7 (Authentication failure)
xscreensaver: 18:26:04: pam_setcred (...) ==> 0 (Success)
xscreensaver: 18:26:04: pam_end (...) ==> 0 (Success)
Note that pam_acct_mgmt retured 7 (PAM_PERM_DENIED). So unless
- xscreensaver.pam includes also "account include system-auth"
- xscreensaver adds new configuration option to actually check account module
on pam or not
this change will break xscreensaver's default behavior.
Mamoru
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
