in reply to Obfuscate my perl code

The problem with using a scipt to obfuscate your code is that a script can only do things like change variable names, remove comments, remove whitespace and un-needed parens. But the real trick to obfuscation is using side-effects (documented and un-documented) and cleverly named variables (like $= and $;). Plus obfuscated code often uses comments to distract the viewer. Thats all rather hard for a computer to think out.

And of course, all the person on the other end needs to do is run your code past the Deparser, and take the resulting code and insert appropriate whitespace and variable names. Failing all that, they could just post it here and someone is more then likely to post an explanation.

My suggestion is to embed your code (and the Perl Interpreter) into a C program and compile it. This is the best way to prepare code for distribution. (And even that can be decompiled.)

Replies are listed 'Best First'.
RE: RE: Obfuscate my perl code
by AgentM (Curate) on Oct 27, 2000 at 20:43 UTC
    eh? What would embedding perl in c accomplish? The perl is still stored as strings- uncompiled. That would end up as zero difference to a hacker. perhaps you meant to refer to Malcolm Beattie's perl compiler which would do a much better job of assembler obfuscation, which is really the trick for ALL commercial software.
    AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.