How about stunnix, folks, does anyone have any experience with their product?
--Ali Isik On 8/23/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
On Aug 23, 2006, at 8:01 AM, Miha Lampret wrote: > Hello all, > > I am writting web application for mod_perl which will be installed > on client's server. Application is almost finished and now I am > wondering which is the best way to protect source code. > > Already checked Module::Crypt but cound't get it to work. It > doesn't create any output file. I came a cross with schroud+ perl > obfuscator which looks ok, but I would like protect strings too. By > strings I meen text that is hardcoded in source and it is printed > to web application user. Do you have any experiences with other > obfuscators or converters to XS code? > > Any information is welcome. > > Thank you, > Miha Best way- fill it with copyright notices, use a restrictive license, get them to sign a document. That's really the only way to protect perl code-- by legally protecting it. And then suing the ass off of your client if they break it. You can not 'protect' perl source the way you are likely thinking. All you can do is obfuscate it, and that is easily broken. You can compile it (perlcc or activestate), but then someone who wants it / needs it bad enough will decompile it.
