Re: protecting your php code from other peeping toms?
| From: | Christopher William Wesley | Date: | Thu, 11 Oct 2001 01:05:27 +0000 |
| Subject: | Re: protecting your php code from other peeping toms? | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-70749@lists.php.net to get a copy of this message | ||
On Wed, 10 Oct 2001, newsgrp@OneGeek.com wrote:
> My question... I want to create some great php code and install it on web
> sites for my clients. Now, this code is my property and I'd like to keep it
> that way. What are my options for securing this code from other eyes? I
Zend Encoder - http://www.zend.com/store/products/zend-encoder.php
PBC (Beta) - http://pbc.sourceforge.net/
> So right now the problem seems to be that PHP code is hard to protect
> because it is in plain text. There is a solution to that -- zend optimizer.
> I looked into that a bit. Unfortunately it does not fit into the open
> source category and is quite expensive (US$2,400.00 -- or maybe I
Neither does your philosophy of restricting access to your code. The Zend
developers make a good product that you can use to protect your assets.
If your code is worth what you make it out to be, look at the $2,400 as an
investment into yourself and your own code.
> misunderstood and it is only 24.00 =). So that seems to be out of the
> option for most people.
Mostly freeloading people. People who have code they value more than
$2,400 will glady ante up for the investment. People seeking optimization
of encoded PHP will ante up for the investment. Open source developers
who don't worry about that level of optimization don't really have a
reason to have their code encoded. Freeloaders want the Zend Encoder for
free (or cheap) so they can exploit Zend deveopers' code/product to
protect their own.
~Chris /"\
\ / September 11, 2001
X We Are All New Yorkers
/ \ rm -rf /bin/laden