Bug 212830 - x11/xscreensaver: enable PAM by default
Summary: x11/xscreensaver: enable PAM by default
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Niclas Zeising
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-19 17:51 UTC by Eric van Gyzen
Modified: 2020-04-01 20:37 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric van Gyzen freebsd_committer freebsd_triage 2016-09-19 17:51:04 UTC 
I use xscreensaver on my workstation at work.  We use LDAP (AD) for user
accounts, so I have to build xscreensaver with PAM support.  This is the only
package that I need to build from the port; all others I can simply install from
prebuilt packages.  Would you consider enabling the PAM option by default?  It
would definitely be more convenient for people in "enterprise" environments.
Comment 1 Niclas Zeising freebsd_committer freebsd_triage 2016-09-22 09:14:32 UTC 
Hi!
Which version of FreeBSD are you using?  There's a PR report about xscreensaver and pam not working on FreeBSD 11, so I tohugh it'd check what you are using first.
Comment 2 Eric van Gyzen freebsd_committer freebsd_triage 2016-09-22 12:59:44 UTC 
I'm on 11-STABLE right now:

FreeBSD 11.0-PRERELEASE #0 r305779+e1bcca4(stable/11): Tue Sep 13 15:15:04 CDT 2016

This machine ran multiple 10.x releases, then 11-CURRENT, then 11-STABLE.  I've never had trouble with xscreensaver and PAM.  I lock and unlock my workstation several times every weekday.

$ pkg info xsc\*
xscreensaver-5.35

Let me know if you need more information.
Comment 3 Walter Schwarzenfeld 2018-05-24 13:55:15 UTC 
Is this still relevant?
Comment 4 Eric van Gyzen freebsd_committer freebsd_triage 2018-05-24 14:00:18 UTC 
Yes.  The situation has not changed.  I would still love to see xscreensaver built with PAM.
Comment 5 Eric van Gyzen freebsd_committer freebsd_triage 2018-11-27 19:52:51 UTC 
I would still like to see this change go in.  This is an impediment to using FreeBSD in a corporate network, especially Active Directory.
Comment 6 commit-hook freebsd_committer freebsd_triage 2020-04-01 20:36:06 UTC 
A commit references this bug:

Author: zeising
Date: Wed Apr  1 20:29:43 UTC 2020
New revision: 530240
URL: https://svnweb.freebsd.org/changeset/ports/530240

Log:
  x11/xscreensaver: Update to 5.44

  Update x11/xscreensaver to 5.44
  Enable PAM by default [1]

  Changelog:
  https://www.jwz.org/xscreensaver/changelog.html

  PR:		212830, 211424 [1]

Changes:
  head/x11/xscreensaver/Makefile
  head/x11/xscreensaver/distinfo
  head/x11/xscreensaver/pkg-plist