> There should be no security concerns, though make sure if you turn it
> one that it doesn't take effect if EXEC_DEFAULTS or EXEC_SECURE is
> set.
Sigh. So many things for Thomas to forget, so little time. No, wait, he
is addressing that problem. The concern had to do with inheritance of the
EXECSERVERS environment variable, and that's why there is magic someplace
(or was going to be? I'm not near my sources right now) to excise the
variable from the environment on EXEC_SECURE (not just ignore it in exec).
We did think it all over before and come up with solutions we thought were
ok, but that is a far cry from it not being a whole can of worms fraught
with potential security concerns.
> IIRC it was commented out because of some bug in scanning the
> environment.
That much is undoubtedly true.
