FS#5272 - xlockmore should make use of pam
Attached to Project:
Arch Linux
Opened by Christian Schmidt (mucknert) - Monday, 21 August 2006, 20:16 GMT
Opened by Christian Schmidt (mucknert) - Monday, 21 August 2006, 20:16 GMT
|
Details
The current state of affairs is that xlockmore asks for a
password the first time you run it and stores it in its
configuration-file. I believe that this is an awkward
behavior and should be changed. In fact, on most systems
(except Arch) xlock works the way that it uses the User-PW
provided by pam. This can be fixed easily by adding
--enable-pam to the PKGBUILD.
|
This task depends upon