php开源屠龙刀
梅花三弄dezend v1.1
[color=#FF0000]主要增加对用zendguard 4.01进行加密的dezend支持[/color]该类文件开头格式：
<?php @Zend;
4147;
现改为：首行包含Zend的文件为需dezend文件

*****************************************
梅花三弄dezend v1.0
一、特点:
1.基于"黑刀4.3"作为内核,[color=#FF0000]支持单文件、多文件、整站或多站.样子如大家非常熟悉的flashfxp,[/color]你可拖动鼠标快速选择多个文件或文件夹.
2.[color=#0000FF]重建原目录结构,目录层数不限,判断是否是zend文件,避免重复dezend,非zend文件也copy至相应目录,保持与原站点整体目录结构和文件数量一致[/color],如所有文件dezend成功可直接整站测试.
    针对目录数量多,文件数量多的大站型需dezend来说,本工具是最佳选择.
3.方便快捷,拖动鼠标选定一批目录或文件后从左边拖到右边或从右边拖到左边即可,可视化人性化操作方式（与flashfxp使用方法基本相同）;
4.支持带空格目录路径或文件名和长文件名
5.支持定制dos执行参数,并可显示dos执行后的返回信息
6.支持dezend后自动执行一批替换,实现扩展式二次dezend,不用于dezend也是一个强大的批量替换工 具，历遍文件夹把选定的后缀文件进行替换
7.使用内存少,单进程目录历遍,不过速度远比平时上传文件快一些
8.支持中途暂停和继续执行
9.支持任务列表保存和恢复
10.智能记录当前操作目录
11.本软件绿色，下载后可直接使用，运行后仅在桌面生成一个快捷方式，不对其它有操作
12.增加黑刀版的config.ini缺了一批关于mysql的函数名,当然也缺了日期时间方面的，暂没有补上
13.支持鼠标右键菜单的全选、取销全选，建立目录、删除文件或目录（与flashfxp使用方法基本相同）
14. 支持双击打开上级目录、双击本窗口打开目录、支持双击调用相应程序打开文件进行编辑（与flashfxp使用方法基本相同）
二、备注：
1、主要用了"黑刀4.3"作为内核，大家可下载其最新版，并把本压缩包mh_dezend.exe和Change.ini及两个图标放到根目录即可．
2、基于核心程序的原因，整站dezend后不一定能使用，需要一定的修改技术，尤其是对高版本的php的function未能很好的dezend,当然不影响

运行，但可读性差。
3、本版免费使用，无功能限制，一切后果自负
4、本想上传一图片和使用教程和实例的，....感觉上一看即会的,觉得不是很必要,请使用之后帮忙上传
5.这是第一个测试版，可能会有一些错误的，望各位用后提出建议，以进一步改进。

三、自我评价:是dezend的一把最新屠龙刀,当然如黑刀兄弟所说：[color=#FF0000]刀可用来切菜，也可用来杀人,请各自注意合理使用[/color]
四、使用注意事项：
1.可把需dezend的文件复制到程序目录下的"zend文件夹,打开主程序拖到另一目录即可，也可点击A、B目录按钮选取源目录和目标目录,选取目

录后，下次打开将自动定位到这两个目录
2.点击“上级目录”虽然可以改变目标目录或源目录，但不会记下这方法打开的当前目录，下次打开仍以最近一次用点击A、B目录按钮选取源目录和目标目录进行定位.
3.要是你对dos命令执行参数不是很熟悉，用默认设置即可，也可参照一下压缩包内附的使用说明里《执行dos命令解密参数详解》(摘自黑刀4.3版使用说明)

梅花三弄QQ：279491263
************************************************************

====执行dos命令解密参数详解(摘自黑刀4.3版使用说明)====

[{/}|{-}command[:attributes]]

/h or /? help （帮助信息）
/detail{/d} show detail（显示详细源代码和opcode信息，非常有用）
/opcode show opcode（opcode数值）
/oparray show oparray（oparray信息）
/function show all the function（所有内部函数名）
/class show all the class（所有内部类名）
/hash show all known hash table（所有认识的哈希表）
/info log general infomation(default phpinfo.log)（其他一些信息）
/raw{/r} dump raw op code（显示详细原始opcode信息，遇到exception的时候非常有用）
/execute execute the file(default NOT)（运行源文件）
/backup{/b} backup the file with extension .bak if out file exist（替换前备份）
/append{/a} appaned to previous log file（追加日志，默认是替换）
/tick{/t} show tick span（显示时间消耗）
/noexpire ignore file expire（忽略文件是否过期）
/noindent ignore indent（去掉缩进）
/compact dump with compact style[not support yet]（暂未使用）
/classic dump with classic style[not support yet]（暂未使用）
/bug dump bug statement（显示BUG）
/full set to full mode（暂未使用）
/force{/f} set to force mode（和/i使用时强制导入config文件）
/import{/i} import class and function name[obfuscate name] from config file（程序根据源文件混淆与否决定导入config文件）
/export{/e} export class and function name[obfuscate name] to config file（导出函数名和类名到config文件）
/obfuscate dump obfuscate name and its url encoded name（显示被混淆的名字）
/dic dump obfuscate name dictionary depend on $level（生成混淆名字典，根据level设置字符数范围）
/tab dump with tab prefix(default space)（使用tab缩进，默认使用空格缩进）
/indent:$i dump with indent $i(default 4)（缩进字符数，默认是4）
/stack:$i dump with stack size $i(default 16)（内部堆栈起始字节数，默认16）
/string:$i dump with stack string length $i(default 4096)（内部字符串堆栈字节数，默认4096，如果内存充裕，可以设大）
/level:$i,$j dump with decode level range $i-$j(default 4-1)（混淆相关的字符数范围，用来猜测名字的字符数范围）
/ext:$ext dump to file with file extension $ext(default .de.php)（输出文件扩展名，*表示使用源文件扩展名）
/root:$root dump to $path + ( $source - $root ) if specified /path:$path（截取路径根路径）
/path:$path dump to $path（输出路径）
/file:$file dump to $file（输出文件名）
/config[:$c] override config file by ?[:phpinfo.log])(config文件名，默认是config.ini）
/log[:$name] override log name by $name([: ?])（日志名）
/logtype:$t override log type by $t<file|registry|debug|messagebox>（输出日志方式，文件、注册表、debug字符串、对话框）
/ini[:$ini] override php.ini search path by $ini([:.], if not specified)（php.ini的优先搜索路径，默认是.,即当前目录）

Enviroment string PHP_DECODE_XXX override default setting, see help(命令行参数都有对应的环境变量）
Priority(high->low):
Command line->Enviroment string->default setting（优先权：命令行 高于 环境变量 高于 默认设置）

if $ext set to *, then keep origin file extension
if $path = 'd:\', $root = 'e:\', then 'e:\php\xxx'=>'d:\php\xxx'

 sigma smp8634/8635 toolchain rootfs building source.

=================

Readme.txt

=================

This is the Sigma Designs customization of the root file system for the

SMP86xx family of chips.

This package is of course heavily depending on the toolchain and kernel

packages.

Quick HOW-TO

============

a) You need to have a working toolchain package. Once you have built your 

   toolchain, be sure to source toolchain-path.env. This is required for you to

   be able to build the rootfs package.

b) Untar the rootfs package.

c) First, configure your root file system: 'make menuconfig'. All the options 

   in the configuration menus have detailed help. Once you are satisfied with

   your choice of options, exit and save the configuration.

d) If you are using the toolchain composed of gcc 3.4.2, binutils 2.15.91.0.2,

   and uClibc 0.9.27 (defined in the toolchain package) then you must select

   Busybox 1.00 from the 'Package Selection for the target --->' menu.

   If on the other hand you are using the toolchain composed of gcc 4.0.4,

   binutils 2.17, and uClibc 0.9.28.3 then you must select Busybox 1.5 from

   the 'Package Selection for the target --->' menu.

e) If you chose to customize your root file system (option 'customize' in

   submenu 'Package Selection for the target'), be sure to prepare your custom

   files now.

f) Run 'make' to produce your root file system.

IMPORTANT NOTE: as of this release, the only supported option in the 'Target 

Options' menu is 'cramfs root filesystem for the target device' (with all its

suboptions). Any other option is currently unsupported and some are known to

not work.

Once you are through with step e), your root file system is available in the

main directory of the package as 'root_fs_mipsel.cramfs'.

Note about the integration with the toolchain and the kernel source packages

============================================================================

The rootfs package is now integrated with the toolchain package and the 

kernel source package and is able to interact with them in the following

ways:

 a) it can grab the necessary runtime libraries from the toolchain package.

 b) it can receive the kernel modules and support files from the kernel source

    package.

 c) the kernel source package can use the produced rootfs image for its initial

    RAM disk.

For interaction a) to take place, the SMP86XX_TOOLCHAIN_PATH environment 

variable must be defined and it must point to the main directory of the 

produced toolchain. The easiest way to achieve that is by sourcing the

'toolchain-path.env' environment file after it is produced at the end of the

toolchain production.

Note that defining SMP86XX_TOOLCHAIN_PATH is not optional. The build will not

go through unless the environment variable is defined and points to a correct

location. This is because, even if the build went through, the resulting root

file system would be unusable as it would not provide *any* run time library.

For interactions b) and c) to take place, the SMP86XX_ROOTFS_PATH environment

variable must be defined and must point to the main directory of the rootfs

package. The easiest way to achieve that is by sourcing the 'rootfs-path.env'

environment file after it is produced, right after your run 'make' or 

'make menuconfig' for the first time.

When SMP86XX_ROOTFS_PATH is defined and points to a valid location, the kernel

source package is able to:

 b) install its modules to the correct location under the customization 

    directory ('package/customize/source') in the rootfs package. In order to

    then make sure the modules end up in the produced rootfs image, you must

    select the 'customize' option under the 'Package Selection for the target'

    menu in 'make menuconfig'.

 c) grab the produced rootfs image (root_fs_mipsel.cramfs) and use it for its

    initial RAM disk.

Thus, in order to produce a rootfs holding the kernel modules and use it as the

kernel initial RAM disk, you need to go through the following steps in order

(note: this is convoluted):

 1) optionally build the toolchain (or use an existing one, more recent than

    2.6.90.0)

 2) source toolchain-path.env in the toolchain package directory

 3) configure the rootfs package with the 'customize' option on in the

    'Package Selection for the target' menu

 4) source 'rootfs-path.env' in the rootfs package directory

 5) configure the kernel, review what is configured as modules, 'make dep'

 6) 'make modules' in the kernel source directory

 7) the 'modules_install' target for the kernel needs that the system map be

    already produced. In order to achieve that, build a first version of the

    kernel: 'make vmlinux'

 8) 'make modules_install' in the kernel source directory. The modules are now

    installed in the rootfs package customization directory.

 9) 'make' in the rootfs package directory. You have now produced a rootfs 

    image holding the kernel modules.

10) 'make' in the kernel source directory. You have now produced a linux ZBF

    image with an initrd holding the kernel modules.

Coming features

===============

N/A

Troubleshooting

===============

a) when building the cramfs utility tool, the compiler complains that it can't

   find 'zlib.h' or '-lz'.

   You need to have the development version of zlib installed on your system.

   How to do that depends on your distribution.