Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

comment on

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

I know this horse has been beaten and there is plenty of info out there.

I'm curious if anyone is using obfuscation via Acme::Eyedrops for production code. I've been doing it for a long while now and I'm looking for liabilities in doing so. I do have some complicated code, but have not had anything blow up. I'm using TrapEvalDie and I created a shape that is nothing more than 60 '#' in one line. In my build process I've created a dependency of .pl to .eye. I'vw written a utility that converts the .pl to .eye vua eyedrops. It creaets a new file with the shebang, copy wright info, date/time converted, and contact info. Below that is the conversion. The covnersion can make the code 10x greater in size. The code runs on an embedded device and loads from a lzma squashfs ram disk. So far the only liability I've found is longer load time.

I'm not too concerened about the users attempting a reverse enginner. I'm practicing sercurtry thru obsecurity. The conversion process also allows me to run a syntax check on the code at build time and prevents me from sending wrong code to the device.

So, I'm want to know issues of Acme::Eyedrops in production and waht liabilities I need to be aware that when converted could cause me issue.

Thanks, Chris

In reply to Production obfuscation by linxdev

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

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

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (1)
As of 2021-08-01 13:03 GMT
Find Nodes?
    Voting Booth?
    My primary motivation for participating at PerlMonks is: (Choices in context)

    Results (7 votes). Check out past polls.