I put the delete in. Once the error had gone I commented that line out to see if it was necessary and the error did not return.

Sorry, since your example didn't include the delete, I interpreted that to mean that you hadn't used it. (I've only got what you show me to go on, so that's not an unreasonable interpretation.)

My first experiment didn't have the delete but did change the PATH, and it wasn't sufficient to remove the taint message; my second experiment added the delete and the taint message went away; in a later experiment, I accidentally forgot the delete, and the taint message came back. So I don't know how the taint message went away for you. I would personally be worried that it will come back unexpectedly; since it doesn't hurt to leave it in, that would be my recommendation.

In reply to Re^5: Insecure CPAN module in taint mode by pryrt
in thread Insecure CPAN module in taint mode by Bod

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.