php_screw installation and usage tutorial (another PHP code encryption implementation)_PHP tutorial

Before we start, we must first clarify two issues: First, supporting open source does not mean opposing code encryption; second, it is even more inappropriate to open source things that do not belong to you (such as the company's).

As I know before, Zend’s encoder is used to encrypt PHP codes. This is not only a commercial software, but it seems to have problems that can be cracked, so I found an alternative solution────php_screw, a Stuff developed by the Japanese.

php_screw is very small. I have not read its algorithm carefully, but from the documentation, you can change the SEED yourself, and then compile the so and executable files yourself. If you are good enough, you can even change the algorithm yourself. In any case, for us "ordinary people", this kind of encryption should be enough. If you really want to be watertight, it's better not to make it public. Although the author said that it is not easy to crack, I don't know where it is. What about the cattle, right?

The installation environment requires: PHP5.x, zlib enabled, autoconf, automake installed.

Test environment: Ubuntu 8.04 hardy, PHP 5.2.3.

Download address: http://sourceforge.net/projects/php-screw/

1. Unzip and change my_screw.h. The numbers inside are SEED, which is equivalent to a password. You can change or increase it at will, and the number of numbers does not affect the decryption speed.

2. Compile the so file:

Copy the code The code is as follows:

$ phpize
$ ./configure
$ make

If such an error occurs, it is because autoconf is not installed:

Copy the code The code is as follows:

$ make
make: *** No targets specified and no makefile found. Stop.

3. Install the so file, and copy the compiled file in the modules directory. Go to the location where the php extension is stored, such as /usr/lib/php5/20060613+lfs, and then add in php.ini:

Copy the code The code is as follows :

extension = php_screw.so

4. Compile the executable file used to encrypt files:

Copy code The code is as follows:

$ cd tools
$ make

The newly generated screw in the tools directory is just the screw, which can be called after putting it in $PATH, for example To encrypt a file:

Copy the code The code is as follows:

$ screw a.php
Success Crypting(a. php)

The encrypted a.php executes normally, and screw will also rename the original unencrypted file to .screw file as a backup.

Update @ 2008-09-01

After encryption, there is still a small problem. When you use require or include to reference the encrypted code placed under include_path, it will be quoted as clear text. There are two solutions:

Use an absolute path to reference the encrypted content placed under include_path. If it is your own host, it will definitely be no problem;
Use a relative path to reference, such as in a subdirectory of this project, this is also no problem.

http://www.bkjia.com/PHPjc/778127.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/778127.htmlTechArticleBefore we begin, we must first clarify two issues: first, supporting open source does not mean opposing code encryption; second, , if you open source things that do not belong to you (such as the company's), it will be even more...