https://bugzilla.redhat.com/show_bug.cgi?id=1676961
--- Comment #6 from Thomas Walker Lynch <thomas.walker.lynch(a)gmail.com> ---
I am having some difficulty parsing that prior message as it appears to speak
to a different context than that of system programming in C and making system
calls from a set uid program. I do not think that comment would be relevant to
this issue, and I hope you would not close the ticket based on not grocking the
issue rather than based on understanding the issue and providing an explanation
- though I do not think there is an explanation. Sudo's behavior relative to
zeroing out the inherited uid to zero and running as root makes it impossible
to write programs to help users to do system tasks. The inherited uid should
be left as the user who started the sequence of events, so that the setuid
script can know who it is working for as it does system stuff. The current
behavior also kills the audit trail, by zeroing out the inherited user id, the
user who begins the mischief becomes anonymous. -Thomas
--
You are receiving this mail because:
You are the assignee for the bug.