Hey, I'm having troubles getting File::Path to run in a script with taint checking.

The values I pass in are taint safe. It seems the values it pulls out of a readdir are not though, as it dies on unlinking a file in a subdirectory of the file I pass in.

Has anyone else had this problem?

Here is a simple script that also has this problem:

#!/usr/bin/perl -wT use strict; use File::Path qw/rmtree mkpath/; rmtree(untaint_filename($ARGV[0]), 1, 1) or die "Could not rmtree $ARGV[0]: $!"; sub untaint_filename { my ($filename) = ($_[0] =~ m!^([\w\d\-_/\.]+)$!) or die "$_[0] is not safe."; return $filename; }
Do the following (on unix) to test it:
mkdir -p blah/blah/blah/blah touch blah/blah/foo touch blah/blah/bar touch blah/blah/blah/foo touch blah/blah/blah/bar ./test.pl blah
btw, I'm running perl 5.6.0 on linux with File::Path 1.0403

In reply to File::Path and Taintedness by DrZaius

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.