- User Since
- Jun 10 2015, 7:12 AM (381 w, 1 h)
May 24 2017
May 18 2017
could you check in some app, started in e with the bug, what the TracerPid of > /proc/<pidof that app>/status tells you?
Starting e directly:
May 17 2017
Will give it a shot...
Hmm... Seems you're right: /proc/*/status:TracerPid is non-zero only for enlightenment. However, as soon as I start a shell outside enlightenment_start's tree, suid starts working as expected. I bet this is some systemd supporting patch that makes the entire process group inherit something unexpected (?) from the leader
It seems that enlightenment_start is ptrace-ing all its child processes and (root) suid binaries won't change their euid to 0 causing sudo, pam, etc. unusable. I can reproduce this specific scenario on other kernel versions ('strace -o /dev/null sudo ls' from a console/tty). I wonder why this isn't visible with enlightenment_start for kernels <v4.11