Bug 2126
Summary: | xscreensaver cannot check password (xscreensaver-3.08-4) | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | rh2021 |
Component: | pam | Assignee: | David Lawrence <dkl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | davem, msw |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-05-06 14:48:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
rh2021
1999-04-11 17:57:00 UTC
Downgrading pam to pam-0.66-4 fixed the problem. Something between -4 and -11 is causing xscreensaver to not "work". using xscreensaver-3.08-4 & pam-0.66-11, xscreensaver prints those error messages on startup, but does lock and unlock the screen correctly (this is in the test lab). What does your /etc/pam.d/xscreensaver say? *** Bug 2164 has been marked as a duplicate of this bug. *** The update to xscreensaver-2.0.9 in the current build cases the password entry prompt to always fail. To reproduce: lock screen, tap a key, try to enter user's password, it will always fail ------- Additional Comments From notting 04/13/99 10:06 ------- Arrgh. Everyone can duplicate this except me. - are you using shadow passwords (I'm assuming yes) - are you using NIS (I'm assuming no) What version of PAM are you running? It looks like we might have to turn the setuid bit back on. *** Bug 2164 has been marked as a duplicate of this bug. *** The update to xscreensaver-2.0.9 in the current build cases the password entry prompt to always fail. To reproduce: lock screen, tap a key, try to enter user's password, it will always fail ------- Additional Comments From notting 04/13/99 10:06 ------- Arrgh. Everyone can duplicate this except me. - are you using shadow passwords (I'm assuming yes) - are you using NIS (I'm assuming no) What version of PAM are you running? It looks like we might have to turn the setuid bit back on. ------- Additional Comments From pbrown 04/13/99 16:59 ------- *** This bug has been marked as a duplicate of 2126 *** This seems to be a bug in /sbin/pwdb_chkpwd, as xscreensaver is properly doing pam authenticate calls. fixed in some later pwdb release before 6..0 |