http://www.nntp.perl.org/group/perl.perl5.porters/2006/03/msg110348.html
I am just getting back into analyzing the test results for VMS, and it
appears that now if perl is run with "-T" that on VMS $ENV{PATH} is
tainted, and I have been unable to remove the taint so that the runperl
subroutine will work.
The test t/op/utftaint.t is failing for me after test 87 with an
Insecure directory in $ENV{PATH} every time.
When we looked at this before, it was working for Craig if the logical
name for PATH existed before the test was run and it had certain values.
I was not able to come up with that article through a google search.
In testing, it appears that if $ENV{PATH} does not exist, which is the
normal condition on VMS, the perl statement 'local $ENV{PATH}' creates
it, and makes it persist in VMS in the process logical name table after
Perl has exited.
I have commented out all references to $ENV{PATH} from t/op/utftaint.t
and t/test.pl with no change in the behavior.
It is looking like there is no way to untaint the PATH environment variable.
I suspect that tainting and VMS environment variables have some
unexpected interactions that need to be better understood.
-John
[EMAIL PROTECTED]
Personal Opinion Only
