From what I can tell, -i has to actually appear on the command-line
$ cat uhoh
#!/usr/bin/perl -i.bak e die(666)
$ perl uhoh
Can't emulate -e on #! line at uhoh line 1.
which hopefully self-limits its significance as a tool for exploit.
Hmm, the only exploit situation i an envision is someone naively automating perl, for example from perl
system $^X, "-i$bak", ...
which doesn't seem unreasonable.
I suppose given that -e commandline documents
$ perl -e warn(1); -e die(2);
1 at -e line 1.
2 at -e line 2.
folks might be scared away from automating perl this way, but then again whitespace in paths is not unheard of
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||