I'm sceptical about encryption/copyright protection. As long as you control the machine, there are always ways around it, since the un-encrypted product has to show up somewhere on your computer anyway.

The best solution would be to write your own parser/compiler/interpreter, probably. Which is probably beyond the company that came up with this. And it's still not a guarantee for full code protection.

The only way these schemes can be made practically impossible to work around (for mortals like me, that is ;) ), is by coming up with hardware implementations, so that the data can be encrypted from the content provider all the way through uhm... speaker, processor, soundcard, whatever's appropriate. And even then there are still ways to re-route the signal or grab the memory.

So no, I don't think it's reliable in a technical way. But legally, that's a different matter. You clearly had to break the encryption to get access to the code, so you showed 'malicious' intentions and probably broke the EULA or whatever agreement, too.

IMHO, this is both a technically stupid and morally ridiculous way of protecting IP rights (note: I'm pretty pro opensource software)... But I comfort myself with the idea that it's going to fail anyway.

In reply to Re: Encrypted Perl? by december
in thread Encrypted Perl? by jens

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.