Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Just keep down-voting, mein enemy.   Just keep down-voting.

(Maybe “the usual seven” could write a short Perl script to query all 4,329 of my posts so-far, and, if all of you ran this script to down-vote every single one of my posts, then maybe you will finally succeed in down-voting me completely off the island ...   Woo, hoo!)

Otherwise, please listen up . . .

Otherwise, I stand behind my original comments without further comment.   The OP knows little about security, is blanched by the number of CVE reports that have been logged with regards to Perl, and really does want information and assurance.   Not too much of interest has so-far been said in this thread, hence my comment.   First, that there is nothing particularly special ... nor, categorically “vulnerable,” about Perl.   And, that most interesting exploitable-things occur at the operating system level, not the application.   Merely overflowing a buffer will not get you root, and so on.

And, in my second paragraph, underscoring the human(!) factor.   It has usually been my experience over these many, many years ... and, believe it or not, it’s getting close to forty ... that security breaches which were initially ascribed to “external” sources, almost always turned out to be “internal.”   My client-before-this also had the experience of realizing ex post facto that he had unwittingly hired a convicted felon on probation.

I will also, incidentally, stand behind all of my previous, cited by you, posts, as well.   Not the way that you would have responded to the same thread?   Goody for you.   There is(!) “more than one way to do™” a great many things in this world including, replying to a thread.

In reply to Re^3: Perl Security Testing by sundialsvc4
in thread Perl Security Testing by zentara

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, 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
  • 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (6)
    As of 2019-08-21 15:28 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found