4.4. Obfuscation
Some strings remain in the PHP bytecode stream after encoding. For example, local variable names are present after compilation. To prevent these strings from appearing in encoded files, the Encoder features an optional obfuscation processor that is used after the PHP source has been encoded to compiled bytecode.
Obfuscation options
The checked boxes determine which aspects of the compiled PHP bytecode will be obfuscated. Currently line numbers, global function names and local variable names can be obfuscated. The Obfuscation key should contain a secret phrase to be used when obfuscating strings. The obfuscation algorithm is a one way process that would require a brute force attack and knowledge of the key to reverse.
Obfuscation exclusions
While it can be desirable to obfuscate function names, it is sometimes necessary to prevent certain functions from being obfuscated. Such cases include functions in non-obfuscated code that are to be called from obfuscated code, functions in obfuscated scripts that are to be called by unencoded scripts, and functions in obfuscated code used as callbacks to builtin functions.
To specify these exceptions, a text file should be created with the name of each function occuring one per line. The absolute path to this file should be entered in the Exclusion file field.
Blank lines and text appearing after a # character in an exclusion file are ignored.