Re: [dev] [slock] 1.4 no longer working on freebsd with ldap/kerberos

On Mon, Mar 27, 2017 at 6:36 PM, Markus Teich wrote: > The patch format was weird. I fixed it, please try again. The new slock-pam_auth-20161126-9909280.diff now applies cleanly. I have to remove -DHAVE_SHADOW to get it to build, as expected. It still fails to run

Re: [dev] [slock] 1.4 no longer working on freebsd with ldap/kerberos

Trying one more time to bisect this, I ended up at 04143fd68dbc656905714eff5c208fadb3464e25 as the commit that introduced the "slock: getpwuid: cannot retrieve shadow entry (make sure to suid or sgid slock)" error for my environment. This was with replacing HAVE_SHADOW with HAVE_PAM. I tried the

Re: [dev] [slock] 1.4 no longer working on freebsd with ldap/kerberos

On Tue, Mar 21, 2017 at 7:10 PM, Markus Teich <markus.te...@stusta.mhn.de> wrote: > Heyho Andrew, > > Andrew Cobaugh wrote: >> I believe this is related to this change: >> >> >> http://git.suckless.org/slock/commit/?id=04143fd68dbc656905714eff5c208fadb

[dev] [slock] 1.4 no longer working on freebsd with ldap/kerberos

After upgrading from 1.3 to 1.4 on FreeBSD 11.0-RELEASE-p1, slock is saying: slock: getpwuid: cannot retrieve shadow entry. Make sure to suid or sgid slock. I believe this is related to this change: http://git.suckless.org/slock/commit/?id=04143fd68dbc656905714eff5c208fadb3464e25 In my