1. Apparently in the real world, a certain degree of obfuscation (especially chained with other techniques) makes it a bit harder for people to crack AND MOST IMPORTANTLY keeps your pay cheques coming through.
2. You won't find good filters/obfuscators for free very easily.

I don't have much to add to your actual question, but there is something I'd like to bring up. This should have been your original post. What you originally asked -- including your followup "clarification" -- sounds suspiciously like a request that someone do all your work for you. To me, the reaction shows other monks thought the same way. Your Stream of Consciousness node, in contrast, makes it clear that you've put some thought and effort toward the goal, and are just looking for any further ideas. If you'd put this much effort into the OP, I believe you would have received a much better response. Sorry for the meta-discussion, but I thought it might be helpful to hear someone else's take on the situation.

You can also read a pretty good discussion on the topic right here at the Monastery: Why is it bad to hide the source?.

Apparently, you don't want to do what management asked of you. There some things that you can do:

• Let management hire someone to do this assignment
• Convince management to spend some money on a commercial obfuscator. After all, they expect to make money on the product, and often, you have to invest some money before you can reap the benefits. They probably already saved a lot of money by using Perl and CPAN

Arjen

In any case you might want to try "perl source encryption" or something at a google near you if you aren't finding what you want on CPAN.

package SuperDuperObfuscated;

use warnings;
use strict;

use Filter::Simple;

FILTER {
  s///; # don't do jack
}

1;
[download]