|Keep It Simple, Stupid|
Protecting perl source codeby tame1 (Pilgrim)
|on Jul 22, 2002 at 03:40 UTC||Need Help??|
tame1 has asked for the
wisdom of the Perl Monks concerning the following question:
Recently, my employer closed his doors. We were able to talk him into letting us take our laptops. Of course, we had to pay for them. Along with cash, I signed a contract to provide 6.5 hours of contracting services.
Anyhow, he has asked me to look into some methods to protect the source code we developed (all mod_perl/apache).
I tried Conway's Acme::Bleach, but it won't work and does some really STRANGE stuff to httpd.conf and other conf files, all on it's own. Not good.
perl2exe isn't gonna cut it, as I don't want the perl binary embedded into each and every module! The Zend Encoder is strictly PHP. Heck, I can't even find a nice script around here that will at least do a blanket removal of non-essential spaces and carriage returns. That won't really protect the code, but it'd be a real b*tch to undo.
Can anyone think of a product or script that would somehow secure perl source code (other than begging Damian and the other's to make perlcc work with more complex programs than "Hello World" - which won't work anyhow, now that I think about it, since the perl interpreter/compiler is in the apache.)?
What does this little button do . .<Click>; "USER HAS SIGNED OFF FOR THE DAY"