> *** Somewhat off-topic *** > * Obfuscators don't work well enough to bother with. If you can't have > people reading your code, don't use Perl, or better still, use Perl but > don't allow access to the machine where the program runs (e.g. put up a > web interface to a service under your control). >
Agree strongly after I looked at the example encoded and obfuscated output of Stunnix Obfuscator. I was able to bring it back to near original code (some information like original variable names are lost). They might stop the lower 90% of the Perl programmers, but not the type people hire to reverse engineer. Obfuscated code is likely to be poor quality code (lack of pride - bugs hidden away). http://www.stunnix.com/prod/po/sample.shtml Jonathan Paton -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
