At 10:50 PM -0500 8/13/07, John E. Malmberg wrote:
>Craig A. Berry wrote:
>>At 8:14 AM -0500 8/13/07, John E. Malmberg wrote:
>>
>>>Craig A. Berry wrote:
>>>
>>>>At 11:39 PM -0500 8/12/07, John E. Malmberg wrote:
>>>>
>>>>>The last 2 tests in utftaint.t are failing on VMS.
>>>>>
>>>>>Insecure $ENV{PATH} while running with -T switch at ./test.pl line 547.
>>>>>
>>>>
>>>>I don't see this failure with a default configuration.
>>>
>>>Is utftaint.t succeeding with all 88 tests for you?
>>
>>Yes, it is.
>In the process where I am running the tests standalone, path is not explicitly
>assigned by me.
>
>My guess is that it is failing in the tests run as part of the build because
>something is leaving a path value that should not be there. That may be an
>artifact of some of the symbolic link tests that you are not running.
Do have a look here:
http://perldoc.perl.org/perlsec.html#Cleaning-Up-Your-Path
Basically it thinks you are giving it a PATH definition that is
either not absolute or is world writable. Since symlinks are the
main difference between your configuration and mine, do you have a
symlink named "path" lying around?
You might need to step through taint.c:Perl_taint_env in the debugger
to see what it thinks PATH really points to. There are also some
VMS-specific sections in mg.c:Perl_magic_setenv that determines
whether a path qualifies for tainting. Watching it do it's thing in
the debugger would probably turn up pretty quickly what's going on.
--
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
