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
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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

Closed by  Alexander Baldeck (kth5)
Wednesday, 23 August 2006, 09:31 GMT
Reason for closing:  Fixed

Loading...