Hello, I've written a script that works fine with -T, but when i use a backtick command, perl starts to complain. I've tried to untaint this data, but haven't succeeded. Can anyone help me?? I used a simple regex just to check, but it won't help.
my $_suffix = `rsh fs3cm -l ccmroot "/home/ccm_root/bin/UpdateSettings +New.pl -r 62 -d $dbname"`; if ($_suffix =~ /(.+\s+.+\s+.+)/) # Untaint the scalar { $suffix = $1; # Pass the value to this scalar if successfully untai +nted } else # Otherwise exit the program with error message { $message = 'The remote shell command produced an error in this scrip +t.'; &display_page($message); # Create an HTML-page to display the messa +ge exit; } $message = "Database added to $file"; &display_page($message); exit;
Perl doesn't like the first line, even if i untaint the $_suffix variable. Thanx a zillion...

In reply to Untainting backtick command data by Anonymous Monk

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.