Christopher Taylor wrote:
I am new to this list so forgive me if this has already been addressed. What I would like to do is keep a library of php scripts on my site. I would like customer sites to call the functions in my library, but have their server do the work. I would like to keep the proprietary code off of their site. I have been able to do this by changing the extension of the library file from php to inc. Unfortunately, this also makes the library file readable if the user puts the url for the file into the browser. Thanks.
search for 'php encoder' and use one (some cost money). changing an file extension from 'php' to 'inc' does nothing to protect your code in way what so ever - given that you think it does I am left wondering what the value of your proprietary code could be? is it really so great that it is worth the time/hassle/cost of encoding? You might consider merely signing an agreement with your customers that they are not entitled to browse, copy, reuse on other domains, etc - and be happy if they pay the bill ;-) I'm not suggesting what you offer/make is rubbish but merely that you may be making a mountain out of a practical molehill in terms of the security requirement you saeem to be setting yourself.
Chris Taylor
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
