On Wed, 28 Mar 2012, Matthias Drochner wrote:
Should there be a pam configuration file for 'xlock'?Yes, it needs one named "xlock". (I had to look into the source to find out.)Is it intended to use one of the existing pam configurations--"system" perhaps?One with everything delegated to "system" would be sufficient. Have a look at the example in pkgsrc/x11/xscreensaver and the MESSAGE there.
I updated after you added these items and rebuilt with the "pam" option enabled. With the default example "xlock" pam configuration, it still couldn't authenticate to unlock the screen. I then built security/pam-pwauth_suid and adjusted the "xlock" pam configuration accordingly. Only then was xlock able to successfully authenticate and unlock the screen. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]mylinuxisp[flyspeck]com OpenBSD FreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645