When Perl gurus are asked "how do I untaint stuff", they generally answer with "it depends".
Well, it doesn't "depend". There is only one (correct) way to untaint data, and that is by matching it. 
my $tainted = $ENV{PATH};
my $untainted = $1 if $tainted =~ /^(.*)$/;

[download]
What you allow to match is the part that "depends" (it's called data validation).

In your case, it doesn't look like you need to validate data at all (you may need to escape it if you're gonna display it via html, but you should allow the user to enter everything).

PS - on a sidenote, you can untain values like 

my $tainted = $ENV{PATH};
my($untainted)= ( keys %{ { $ENV{PATH} => undef }} );

[download]
but you cannot rely on that behaviour.

In reply to Re: Common untainting methods? by Anonymous Monk
in thread Common untainting methods? by Wally Hartshorn

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.