Re: [dev] [slock] fixing the annoying combination with PAM

Hi Markus,

On 19 April 2011 22:24, markus schnalke <meillo_AT_marmaro.de> wrote:
> at my university PAM is used for user login. They have slock installed
> because they have the suckless-tools package (Ubuntu) installed.
>
> If I run slock , X gets locked like it should. Unfortunately I'm not
> able to unlock it again because slock checks against /etc/passwd which
> does not contain an entry for my account. This leaves me stuck in an
> dead end. This is annoying.
>
> Of course, I could simply not use slock, but you know how things
> happen from time to time ... your habits take over. ;-) Hence I though
> that slock could check for an passwd entry before it locks. Thus it
> can prevent locking the screen when you won't be able to unlock it
> afterwards.
>
> Here is a patch against current tip which implements this check. I'm
> no expert in this topic, I just hacked it to work for me.

Thanks, applied.

I'm not sure I like this approach, but the PAM interface is really bad taste.
Probably we can separate Petr's PAM implementation into a separate
file and pull it in as per compile time option to keep the base of
slock.c nicer, than adding various CPP conditions.

Cheers,
Anselm
Received on Thu Apr 21 2011 - 10:24:42 CEST