@andsild, thanks for your PR! By analyzing the history of the files in this pull request, we identified @edolstra, @xvapx and @rbvermaa to be potential reviewers.

I was slightly unsure of where to put the documentation but I hope this is a good attempt 🙏

Shouldn't we maybe add a programs.slock module instead? That's also done for mtr or wireshark.

@fpletz That sounds even better. I'll try that later and close this PR 👍

Want just to note, that I have in my configuration just

wrappers = {
    slock.source = "${pkgs.slock}/bin/slock";
};

I'm not sure, what is "the right way" though.

@demin-dmitriy Less is better. I thought I had to put in setuid, didn't think of trying just slock.source

Given that the fix for slock is just one line extra to a configuration.nix, I'm tempted to just let this PR rest until I have more time another day. Also, I agree with a comment in #13286 that there should be a more general fix to this so that it is easy for people who get errormessages related to setuid to lookup and identify how to fix it.