The "you neither have the time to keep up with the patches nor want to make the effort" bit smells like FUD to me. While SSH has had its share of problems, it really isn't that hard to keep most GNU/Linux distros up to date. For me, it's either "apt-get update; apt-get dist-upgrade" or "emerge sync; emerge world". It really isn't a big deal.

Perl programs are almost entirely immune to buffer overflows. If you access an array element outside the normal bounds, Perl automatically grabs more memory and builds the array. The Java approach (throw an exception and die) is just as effective for preventing buffer overflows (the other benefits of one approach or the other can be debated endlessly).

If there is a buffer overflow in either Perl or Java, it will be in the underlieing implementation. Further, that overflow may or may not be exploitable from any given program.

This highlights a good point about C: it's a great language for what it was orginally designed for (writing operating systems). It isn't such a great language for general applications.

"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

In reply to Re: Perl and TCP port security by hardburn
in thread Perl and TCP port security by zentara

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.