in reply to Re: Forced resolution of environment variables
in thread Forced resolution of environment variables

That's only "dangerous" in a place were someone else controls your environment. But if someone else controls your environment, even a use strict is "dangerous", as that will allow the attacker to execute arbitrary code on your behalf. (Because the attacker can then set PERL5LIB, PERL5OPT, PERLIO, PERL5SHELL, and some other variables to make life annoying).

Replies are listed 'Best First'.
Re^3: Forced resolution of environment variables
by sgifford (Prior) on Oct 22, 2004 at 18:10 UTC
    Not in taint mode, which should always be used in any code executing on someone else's behalf.