Hi, I don't know if I am allowed to reply to this email, but I thought I should make things clear if that would make the problem more suitable for you guys to understand.
The executable, slock, needs suid of root to be run. That's why I can't just put a `sudo` before `./slock` and run the program. If I do, then I get "Make sure to suid or sgid slock." So, I change the owner of the executable to root user and add suid file permissions. But this whole thing is not very efficient. I have to edit, make, change the owner, change the permission and test the executable. There must be a standard procedure to deal with these situations that I don't know yet. I have reached out to some people who advised me to just work on a root level environment for the whole process. I hope this helps make things easier to understand and help me find out some solutions. Thanks, Enan On Sat, Apr 13, 2019 at 7:57 PM Enan Ajmain <3nan.ajm...@gmail.com> wrote: > > Hi, > > I wanted to try and add a background image to the slock utility. I > have not worked on a project which needs "sudo" privilege. And now I > can't figure out how to work on this. For now, I am doing the > following. > > ``` > make > sudo chown root:root ./slock > sudo chmod u+s ./slock > ./slock > ``` > > I am sure I can use the Makefile to do all this but I have no idea > what the actual standard way to do all this is. Any suggestions would > be appreciated. > > Thanks, > Enan
