secondly, do you want to ensure that your code is only being run on computers that you have authorised?
these are related problems, but each requires a different method of solving it.
the other question that is useful to ask is how many days of effort will be required to secure your program and compare that with how much your clients would value that amount of time being used in development of new features instead?
uru -Dave
Kirk Rogers wrote:
i have a collection of perl modules (running under the mod_perl umbrella) and would like to distribute the application to several different sources (clients with open internet web servers). but i dont want to send it out without at least making it somewhat difficult for some hacker to just simply steal it and load it somewhere else without my consent. what options do i have (if any) to secure the code so that it can't be 'easily' stolen? 'easily' being the operative word here, as i realize it wont be 100% safe no matter what i do. the ideal would be to perhaps encrypt some of the code, maybe a few of the base configuration modules, maybe even the startup.pl file, others?
any suggestions would be appreciated, thanks
