Interesting, but --as I assume-- a lot of the functionality will be placed in modules, they will still have to be provided as regular .pm files and are thus open to inspection and breaking the NDA? Or is this script compiler bright enough to also encrypt all dependent modules?Sorry, I didn't try the script compiler myself (for lack of a C-compiler on my Winbox)
CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
| [reply] |
No, all the script compiler does is encrypt the script with RC4, and pack it into it's own data. When it runs, it unpacks the encrypted code, and exec's it. So if you want to
include modules in the encryption, you probably should gut the module innards, and include them as a package in the main script. Then the whole thing gets encrypted. You also need the Perl installation, as this is not like Par, it only encrypts the script itself.
I'm not really a human, but I play one on earth.
flash japh
| [reply] |