This is a known appropriate restriction of File::Find for 5.5.3, and unlikely to be changed no matter how many times you report it, because it needs to be tainted
since the value is untrusted.
The new versions of File::Find include a user-controllable "I trust this"
parameter for managed untainting, but you use these at your own risk:
`untaint'
If find is used in taint-mode (-T command line switch or if EUI
+D !=
UID or if EGID != GID) then internally directory names have to
+be
untainted before they can be cd'ed to. Therefore they are check
+ed
against a regular expression *untaint_pattern*. Note, that all
+names
passed to the user's *wanted()* function are still tainted.
`untaint_pattern'
See above. This should be set using the `qr' quoting operator.
+The
default is set to `qr|^([-+@\w./]+)$|'. Note that the paranthes
+is
which are vital.
`untaint_skip'
If set, directories (subtrees) which fail the *untaint_pattern*
+ are
skipped. The default is to 'die' in such a case.
-- Randal L. Schwartz, Perl hacker
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|