Red Hat Bugzilla – Bug 167479
xscreensaver can't close cleanly via 3rd party application
Last modified: 2007-11-30 17:11:12 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Description of problem:
Xscreensaver doesn't provide a simple interface for 3rd party applications in order to make it unlock. Its possible from another application to tell xscreensaver to lock (xscreensaver-command -lock), but unlocking isn't possible authentication is required.
Unfortunately, this can be a problem if someone is using a security device which does all the authentication.
One such example is the Wireless Security Lock (http://www.thinkgeek.com/gadgets/security/698d/ and http://www.sitecom.com/products_info.php?product_id=293&grp_id=1).
A clean and simple method to solve this problem, is to add an option like "xscreensaver-command -wslunlock" which cleanly unlocks the display even is a password is required (assumes the Wireless Security Lock has done that already).
A patch is supplied (written by Brian Schau, http://www.schau.com/l/wsl/) which adds the proper command to xscreensaver-command.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. make sure xscreensaver is setup to ask for a password
2. enable xscreensaver and let it lock the display
3. try to cleanly close the screensaver without typing a password once other authentication method has been performed.
Actual Results: xscreensaver can't be unlocked.
Expected Results: idealy, unlock the display.
Created attachment 118414 [details]
Patch to add the -wslunlock option in xscreensaver-command
I forgot to mention that the supplied patch applies to xscreensaver 4.22. Fedora
Core 4 comes with version 4.21, hopefuly it won't be incompatible.
As I said when Brian mailed me about this, this patch is no good. Adding domain-specific knowledge
about this particular device to xscreensaver not a general solution.
The right way to solve this problem is to write a PAM module that knows about your security dongle. It
would go like this:
- xscreensaver is running
- user jiggles mouse
- xscreensaver asks PAM, "shall we unlock the screen?"
- PAM says "yes (because the dongle is in range)"
We aren't likely to commit this type of patch without upstream buy-in.
Thank you all for taking the time to look at this patch.