Re: exec and EXECSERVERS

[Roland McGrath]

> Why is that?  If it's programs that call setuid(getuid()) that have
> this responsibility (as the original poster suggested), then this is
> just fine.  On the other hand, my vote is that it's the setuid program
> itself that always has the responsibility.  

That is a new responsibility that individual programs never had before, so
programs not written with the Hurd in mind will not do it explicitly.  For
the various variables that affect libc, the dynamic linker removes them
from the environment.  So we could have it remove EXECSERVERS too.