| How to use technical GUARD: Javasguard is a good Java obfuscator and is also included in the Enterprise Edition of jbuilder7.
Technical guard is a JavaProgram(A jar package), so you must install JDK first. Before running, you need to set some environment variables. In addition to including the Java execution path in the path, you also need to add D: \ javasguard to classpath. jar (assume that your logging guard. jar in D: \ Alibaba Guard ). It doesn't matter if classpath is not set, but the path parameter must be added through-classpath each time it is run. Prepare the. jar file package you want to confuse after setting the good luck environment. As for how to package the compiled class into A. jar file, I will not talk about it here.
The execution format of technical guard is:
Java logging Guard [input the JAR file [output the JAR file ["retain the script file" [log file] The "Reserved script file" describes the classes, functions, and variable names that must be retained and cannot be confused. The log file is a record file generated after execution, errors and obfuscation information recorded.
For "retain script files", you can set it through a graphical interface rggui. The execution command is:
Java rggui
After running the script, you can enter the JAR file as prompted and select the classes, functions, and variables to be retained. After the script is completed, the "Reserved script file" is automatically generated ". In fact, generally, you only need to keep the name of the starting class to run.
If your jar package uses a third-party function library, such as the Siemens API, you must specify it in the-classpath parameter. For example:
Java-classpath c: \ Siemens \ smtk \ 6688istmb8 \ Lib \ API. Jar mongoguard in. jar out. Jar script.txt log.txt If the logging guard obfuscation fails, you can view the log file for error information.
Here I found a problem, that is, when there is a file like... $1. Class, guard will prompt an error, and then I modified hisSource code, Directly skipping the processing of such files. setting and usage of secure guard in jbuilder7:
the Enterprise Edition of jbuilder7 contains dedicated guard V1.1 and the retroguard-v1.1 directory under the jbuilder7 installation path. In jbuilder7, mongoguard can be called directly. The configuration method is as follows:
click menu tools> Configure obfuscators to configure the obfuscators. Click new in the lower left corner... create a new obfuscator and select the zooguard path to complete the configuration. To use archive builder, click "Wizards-> archive builder ..., select archive type MIDlet (this is only applicable to the J2EE application), and set it step by step as prompted. When Step 1 is set as the obfuscator, select obfuscate the contents of the archive, select the obfuscator for the obfuscator, use the classes specified blow to add the class to be retained (the start execution class is retained by default), and end the setting.
in this way, the obfuscated jar package is automatically generated each time a compilation is made. |
