comment on

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.

CountZero

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

In reply to Re: Protection for Perl Scripts by CountZero
in thread Protection for Perl Scripts by locked0wn

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks