Security of the Java chaos itself
Due to safety considerations, the chaos are used for confusion for the written Java program. At the same time, some confusion actually needs to be registered, and some are required to limit the time limit. How to solve these problems, allow yourself to use these chaos for a long time. We can take a look at the JAR file will find the chaos themselves. You can see a lot of file names without any meaning. In this way, we can first see the manifest file to find the main class to find the main class to confine the primary class, find the main method, no chaos will not confuse the main class MAIN method name, or extract the entire chaos Using the Windows search function, find the string of information such as expired, after the found class file is confessed, and then generate .java original file. For anti-compilation, we can use the display byte code and correspond to the anti-compilation command. Then use the 16-encycloped editor to find the corresponding byte code modification, so that the limitation of the chaos can be canceled. I have made some modifications such as Jshrink, Codeshield, Jobfuscator regrets that there is SMokeScreen not completed
