Bug #248
closed
xscreensaver and locking
0%
Description
I compiled xscreensaver though pkgsrc, with PKG_OPTIONS.xscreensaver=pam
to enable use of PAM so I could lock my screen.
It locks correctly, and I get a dialog box, but it doesn't seem to be able
to correctly unlock - it refuses my password. I've tried creating various
permutations of /etc/pam.d/xscreensaver, but no luck.
Here's the pertinent output from 'xscreensaver -verbose'.
xscreensaver: 13:27:26: pam_start ("xscreensaver", "jsherrill", ...) > 0
(success)
xscreensaver: 13:27:26: pam_set_item (p, PAM_TTY, ":0.0") > 0 (success)
xscreensaver: 13:27:26: PAM ECHO_OFF("Password:") > password
xscreensaver: 13:27:26: pam_authenticate (...) > 9 (authentication error)
xscreensaver: 13:27:26: pam_set_item(p, PAM_USER, "root") > 0 (success)
xscreensaver: 13:27:26: PAM ECHO_OFF("Password:") > password
xscreensaver: 13:27:26: pam_authenticate (...) > 9 (authentication error)
xscreensaver: 13:27:26: pam_end (...) > 0 (Success)
xscreensaver: 13:27:26: password incorrect!
xscreensaver: 13:27:27: grabbing server...
Is anyone else using xscreensaver, and its screen lock?
Updated by LabThug over 18 years ago
<Snip/>
I remember there being a problem on my mail server with pam_unix not
linking lutil. Joerg fixed it back in Feb. I wonder if this is
similar.
http://leaf.dragonflybsd.org/mailarchive/commits/2006-02/msg00050.html
Good luck,
Adrian
Updated by justin over 18 years ago
On Wed, July 19, 2006 5:14 pm, Adrian Michael Nida wrote:
On Wed, 2006-07-19 at 14:17 -0400, Justin C. Sherrill wrote:
I compiled xscreensaver though pkgsrc, with PKG_OPTIONS.xscreensaver=pam
to enable use of PAM so I could lock my screen.<Snip/>
I remember there being a problem on my mail server with pam_unix not
linking lutil. Joerg fixed it back in Feb. I wonder if this is
similar.http://leaf.dragonflybsd.org/mailarchive/commits/2006-02/msg00050.html
No such luck. My copy of that file is up to date. Joerg - should I take
this back to pkgsrc-users@ ?
Updated by joerg over 18 years ago
On Thu, Jul 20, 2006 at 01:30:32PM -0400, Justin C. Sherrill wrote:
On Wed, July 19, 2006 5:14 pm, Adrian Michael Nida wrote:
On Wed, 2006-07-19 at 14:17 -0400, Justin C. Sherrill wrote:
I compiled xscreensaver though pkgsrc, with PKG_OPTIONS.xscreensaver=pam
to enable use of PAM so I could lock my screen.<Snip/>
I remember there being a problem on my mail server with pam_unix not
linking lutil. Joerg fixed it back in Feb. I wonder if this is
similar.http://leaf.dragonflybsd.org/mailarchive/commits/2006-02/msg00050.html
No such luck. My copy of that file is up to date. Joerg - should I take
this back to pkgsrc-users@ ?
No, I think this is a local PAM problem. Did you change anything in
/etc/pam.d?
Joerg
Updated by justin over 18 years ago
On Thu, July 20, 2006 1:07 pm, Joerg Sonnenberger wrote:
No, I think this is a local PAM problem. Did you change anything in
/etc/pam.d?
I added a 'xscreensaver' file, which I copied from 'other'. I did try a
few variations on that, but it should be enough.
If it helps, this is my test scenario:
cd /usr/pkgsrc/x11/xscreensaver
bmake PKG_OPTIONS.xscreensaver=pam install
cp /etc/pam.d/other /etc/pam.d/xscreensaver
xscreensaver -verbose &
xscreensaver-command -lock
(can't unlock)
(ssh in from other computer, 'kill pid-of-xscreensaver')
The xterm where the xscreensaver -verbose command was issues will have a
number of diagnostic messages, including what I pasted in a previous
message.
Updated by steve over 18 years ago
On Thu, 20 Jul 2006 14:35:45 -0400 (EDT)
"Justin C. Sherrill" <justin@shiningsilence.com> wrote:
On Thu, July 20, 2006 1:07 pm, Joerg Sonnenberger wrote:
No, I think this is a local PAM problem. Did you change anything in
/etc/pam.d?I added a 'xscreensaver' file, which I copied from 'other'. I did try a
few variations on that, but it should be enough.
I found this problem too - a chmod +s /usr/pkg/bin/xscreensaver
made it work, but I had been hoping that pam would make this unnecessary.
Updated by corecode over 18 years ago
Steve O'Hara-Smith wrote:
On Thu, 20 Jul 2006 14:35:45 -0400 (EDT)
"Justin C. Sherrill" <justin@shiningsilence.com> wrote:On Thu, July 20, 2006 1:07 pm, Joerg Sonnenberger wrote:
No, I think this is a local PAM problem. Did you change anything in
/etc/pam.d?I added a 'xscreensaver' file, which I copied from 'other'. I did try a
few variations on that, but it should be enough.I found this problem too - a chmod +s /usr/pkg/bin/xscreensaver
made it work, but I had been hoping that pam would make this unnecessary.
no, pam needs the binary to run as root, otherwise it can't access master.passwd etc. a pretty stupid design :/
cheers
simon
Updated by justin over 18 years ago
Solved with :
chmod +s /usr/pkg/bin/xscreensaver