Perhaps it would be a good idea to add a section under the tutorials specifically addressing Perl security issues. Unfortunately, the only node there, which looks pretty good by the table of contents, is written in a language I don't even recognize ((lang: lt) CGI/Perl Script Security). I think it would be helpful to have separate tutorials exploring the potential dangers of functions like system, exec, backticks, open, eval, do, and others addressing security measures such as Safe, Opcode, Taint. Right now there is information available, but mostly it is scattered about through offsite links, manpages and FAQs. I'd bet quite a lot of people could benefit from more in depth analyses of these dangers.


In reply to Re: OT: Secure system development article by djantzen
in thread OT: Secure system development article by simon.proctor

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.