No, I don't really misunderstand -- but perhaps you misunderstood my reply. Yes, it may include source or an optree, but that is not preventing some sort of encoding in the internal representation, as an attempt to prevent reverse engineering at some trivial level. I'm not the greatest of C hackers, though I am one of some regard, and I would have done something to make opcode (or source) extraction non-trivial. Many of these support some form of Crypt voodoo, as say the docs.

In reply to Re: Re: Re: Re: Re: Decompile Perl2EXE back to original source by flyingmoose
in thread Decompile Perl2EXE back to original source by dkarner

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.