Developing module - help

[Green Alert]

I have started a new job at a hosting company and one of the projects I inherited is overseeing the development of a new Miva module in-house. A contractor has done the work, and given me a .mv script and a C installer program. This module is only going to be offered to our hosting customers, not for sale to the world (yet). From what I've been able to gather, each hosting customer that uses Miva has their own Miva installation, it's not a mall situation. I had been thinking that since we'd handle installation of the module we wouldn't have to worry about license keys and whatnot, but now I find out that the module source code would be available in the root directory of each site where its installed and people could potentially find it and distribute on the web, so we will need some sort of license key generation/validation system. Can anyone advise on how to do this? The only thing I've found in the Miva docs on point so far has to do with listing the module on Miva Central, which we aren't planning to do.

[ILoveHostasaurus]

If you write your module for version 4.14 and above, the code will be compiled and not visible to the users. Keep in mind that text strings will still be visible in the module though so don't put any secrets in there. :)

[Bruce - PhosphorMedia]

True, however, the compiled script file is there in the user's HTML doc directory.

Obscurity and lack of usefulness outside of the hosted rehlm, maybe enough security, but...I'd at least attempt some basic security measures such as a simple call to a central location, verifying the IP of the callee. (presuming you would know the IP block you are using. If someone moves outside of your hosting environment, the module should not work.