Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
SLiMlock needs suid #2954
but calling it as root after the session has started does not ‘fix’ the problem.
PS: It would appear that the module is poorly documented. The path has to point to a
I have since figured out what was wrong with the theme: I am using dual head and on login, my X monitor settings were different than after I have already logged in, misplacing everything. I haven't figured out how to get around that but at least I know why it happens.
This only leaves the error messages to deal with.
Okay, further investigation has shown that nixpkgs strips the setuid bit.
Try inserting the following in the derivation:
postInstall = '' chmod 644 $out/bin/slock ls -l $out/bin/slock chmod u+s $out/bin/slock ls -l $out/bin/slock '';
It willl output the right permissions when it builds, but afterwards it’s:
Slimlock now uses pam.
slock has no support for pam. There is no support for suid bits in the nix store because it is world-readable and then every user could use these programs to gain root access.