gnome-screensaver configures with --disable-pam

Sean McNeil sean at
Thu May 4 17:26:48 UTC 2006

On Thu, 2006-05-04 at 12:52 -0400, Joe Marcus Clarke wrote:
> On Thu, 4 May 2006, Sean McNeil wrote:
> >
> > Why???
> >
> > I remember this was discussed about xscreensaver at one time and was
> > fixed.  Is there any reason at all why --disable-pam has been set in the
> > configure for x11/gnome-screensaver?  I took this offensive setting out
> > and I can once more lock my screen.  Naturally, with it in I get errors
> > and it fails to lock because I happen to use PAM with LDAP to get
> > usernames and passwords. Not good.
> It was basically adapted from xscreensaver-gnome to give equivalent 
> default behavior.  The first few releases of g-s didn't do well with PAM 
> anyway.  I haven't tested it recently, but if you know it works, please 
> provide a patch, and the PAM support will be re-done.

That's the easy part. Just take the --disable-pam out.

1) The default is to auto-detect PAM support so if it isn't available,
it does the right thing.
2) If an administrator doesn't want to support PAM with
gnome-screensaver, simply do not have an /etc/pam.d/gnome-screensaver.
3) With --disable-pam in, locking is broken on configurations like mine
and it is dangerous not to lock the screen when configured to do so.

--- Makefile.orig       Thu May  4 10:20:50 2006
+++ Makefile    Thu May  4 10:21:01 2006
@@ -23,8 +23,7 @@
 USE_GMAKE=     yes
 USE_GNOME=     gnomeprefix gnomehack intlhack libgnomeui gnomemenus
-CONFIGURE_ARGS=        --disable-pam \
-               --with-gdm-config=${X11BASE}/etc/gdm/custom.conf \
+CONFIGURE_ARGS=        --with-gdm-config=${X11BASE}/etc/gdm/custom.conf \
                --with-xscreensaverdir=${XSCREENSAVER_DIR} \
 CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include -I${X11BASE}/include" \

More information about the freebsd-gnome mailing list