Make sure to document your objections in writing to the responsible person(s), dateable documents are best. Send them an email to the list of Perl security vulnerabilities, so the have no excuse of "i didn't know" if the fit hits the shan.

If possible, you should also print your correspondance re. the security issues of old Perl versions on a color laser printer. Those printers usually encode some metadata in nearly invisible yellow dots all over the pages, this makes it easier to prove when the documents were printed. Just in case there IS a larger issue that leads to a lawsuit. Data breaches and similar things are hugely expensive, so the company might try to sue you as a scapegoat. Depending on your jurisdiction, you might even be held criminally liable, since you were knowingly running an insecure system.

So be careful with this stuff.

Sidenote: Personally, i always make sure i require the latest major Perl release in my commercial source code. This helps make sure that the systems HAVE to be upgraded ;-)

PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
Also check out my sisters artwork and my rather simple sketches/one-panel comics

In reply to Re^3: Why causes Exception::Class a fat-packed perl application to fail (but works with 5.38) by cavac
in thread Why causes Exception::Class a fat-packed perl application to fail (but works with 5.38) by Darkwing

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.