See
perlsec.
In this case they were looking for a way to bring tainted
data in contact with a system command in a way that was
absolutely safe, but would still trigger the taint test.
If you hit the taint test you bomb out and get a false
value. If you don't then you survive to the true return.
Flip the truth and voila!
Incidentally I disagree with them on their comment about
warnings. Consider the following test:
sub is_tainted {
eval { () = (join('',@_), kill 0) };
if ($@) {
if ($@ =~ /^Insecure dependency/) {
return 1;
}
else {
die $@;
}
}
else {
return 0;
}
}
Not only does this pass warnings, but it at least tries
to handle the possibility of other things going wrong.
(eg a platform where
kill is not implemented...)
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.