Longer answer: There are many modules and other techniques out there to obfuscate your Perl code, but anyone who knows Perl and is even marginally motivated to do so can de-obfuscate it without too much effort. (The exact amount of effort depends on which method is employed and I've never been interested in using them, so I can't offer any advice on which to use beyond "don't bother".)

For more detailed answers: Use the search functions. As already mentioned, this seems to come up every month or two.

This question comes up regularly. The Perl community is founded on openness and the idea of locking away source code seems to bother many people. Without the generosity of many people, we would not have Perl to hack with. The usual response is "you can't do it".

In purely technical terms, that is true. If the computer has the key to decrypt and run the software, a sufficiently clever, dedicated person can recover the keys and decrypt the code. Once you have executable code you can do all sorts of things to clean it up and make it easier to reverse engineer. An absolute solution is impossible. What you need is a "good enough" solution.

I've been using PerlApp to distribute apps on Win32 systems for several years. It works well, it is inexpensive, and is produced by a company that is a good member of the community. It won't make your code impossible to recover, but it does provide easy to transport and install packages that are not trivial to recover code from.

It may be possible to do similar things with PAR-Packer and PAR::Filter::Crypto. PAR is a great tool for packaging Perl code for distribution. I've never tried to use it for code hiding, so I don't know what is possible with PAR in this area.

It is impossible to perfectly protect your code, but these two options should give you a way to come up with a "good enough" approach.