That's easy - apply Filter::Handle to STDOUT and check to see that the data isn't tainted. die() if it happens. This is really about preventing tainted data from going to STDOUT so the name isn't great but hey, it works. Why don't you document it and submit it to CPAN?

package CGI::Taint;
use Filter::Handle 'subs';
use Taint;
BEGIN {
    Filter \*STDOUT,
    sub {
        # Access $_[0] directly so that tainted() can test
        # the actual variable.
        if ( tainted( $_[0] ) ) {
            die "Tainted output could not be written to STDOUT: $_[0]"
+;
        }
        $_[0]
    }
}

[download]

In reply to Re: writing a "CGI::Taint" module by diotalevi
in thread writing a "CGI::Taint" module by cLive ;-)

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.