Yeah sure, I agree that eval is always potentially
dangerous... I figured this is rather well-known. And, I wasn't trying
to spread "great memes" :) Rather, I was simply trying to
generically answer the problem of "Normally, I would use a double
quoted string in my script... now what do I do to arrive at the same
effect when I hold the part in between the quotes literally in a
string, like when having read it from a file?" Nowhere in the OP
was any mention of other people potentially having control over the input.
Along similar lines you'd have to warn people every time they
interpolate some variable into some command like
system "convert $imgname.png $imgname.jpg"
because, if $imgname could potentially come from an insecure
source, they might get into trouble inadvertendly running something like
system "convert ; rm -rf ~/* ;.png ..."
I'd probably even mention it if the danger is obvious, like someone
inexperienced trying to execute code like this in CGI context or some
such, but otherwise... should we always warn?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
