comment on

At this node Copying complete module code into a script monk Daddio wanted to paste module code into a script. merlyn replied pointing to no excuses about not using CGI.pm. This concerns me because at this node A serious security problem with CGI.pm 3.01? it is noted that it seems possible to generate a working CGI.pm with a broken $POST_MAX as this variable is no longer coded in the core CGI.pm code - it is in another module. This opens sites using this to denial of service attacks, and worse the problem appears silent.

With complex modules like CGI.pm 3.0 the core code exists not in one but several interlinked modules. While I am at a loss as to how you can generate the problem described (the fact that there are missing modules should be picked up) I am concerned that cutting and pasting modules may lead to code that works on the surface but has significant security or other issues.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

In reply to The Dangers of Cutting and Pasting Module Code by tachyon

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.


Keep It Simple, Stupid
	PerlMonks