|There's more than one way to do things|
Re: Protection for Perl Scriptsby CountZero (Bishop)
|on Jul 08, 2010 at 07:54 UTC||Need Help??|
some scripts I custom make for a server could probably benefit from tampering eyes
Read that again, slowly ... and think about it for a moment.
Protect from whose tampering eyes? root or the sysadmin's eyes? That is no use: they are god and can probably read, decompile, delete and change anything they want.
The client of the server? He/she/it will never see your module if you have configured the server to run rather than show your module's code.
Someone you have sold/licensed your module to? Then your protection is in the contract and not in encrypting the code.
A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James