note 50058 rejected from function.eval by nlopess
| From: | nlopess@php.net | Date: | Wed, 16 Feb 2005 20:06:28 +0000 |
| Subject: | note 50058 rejected from function.eval by nlopess | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-85134@lists.php.net to get a copy of this message | ||
Note Submitter: alan at andaweb dot com
----
Sorry if this not the way this forum should be used.
I develop PHP code in my own server and port them out to my customer's server at the end. One
obvious problem is source code protection. I am aware of serveral commercial solutions but I just
want to try the following method with eval() first. I'd appreciate if anyone would comment on
whether this is a feasable route.
I intend to use eval() to achieve 'code encryption'. That is, I will 'hide' or
'encrypt' the source code before I deliver it to customer's server. Then, with
password or other mechanism, I will de-cipher the code at the run time using eval().
Is there a big issue with this trend, if we are talking about 1,000 php files?
Thanks in advance...