in reply to tainted entangled hashrefs

The code's filename.txt is a relative path depending on $ENV{'PWD'}. That's tainted. Using an absolute path will settle the problem.

Update: MZSanford is quite right, I missed that angle. Boldra's reply is mistaken that $ENV{'PATH'} enters into resolving relative paths to files. That is, as I say, done with $ENV{'PWD'}.

After Compline,
Zaxo

Replies are listed 'Best First'.
Re: Re: tainted entangled hashrefs
by herveus (Prior) on Aug 22, 2001 at 20:30 UTC
    Zaxo misspeaks... :)
    My empirical studies find that "scalar(<>)" remained untainted so long as <> was empty. Providing a file name tainted it, as did providing standard input. Reading from /dev/null did not provoke the error.
    I found no difference between relative and absolute file names for the open; it all appears to depend on <>.

    yours,
    Michael
[reply]
Re: Re: tainted entangled hashrefs
by Boldra (Curate) on Aug 22, 2001 at 20:20 UTC
    Sadly, that doesn't solve the problem. The warning generated by a bad use of the path is actually Insecure $ENV{PATH}.

    - Boldra
[reply]
[d/l]

In Section Seekers of Perl Wisdom