The Java bytecode can be easily understood. Everyone knows. This afternoon I got a long-awaited JBuilder OpenTools (yesterday 1.0 released, freshly baked! But only 14 days, how to do it ~ @@ #! @ #! # @! @ # %% ^ @, less talking about 140 days!), So I didn't hesitate to put down other work, studying a crack and anti-crack of the software encryption method, combined with some of the previous experience, The composition of the essay is not encouraging everyone ...
Crack:
There are many Java Obfuscator on the market (you can list from Google Category) More famous 4thpass products (huh, fat friends! KBROWSER has been used), don't want money to use jode (jode is Obfuscator is also Decompiler, also provides source programs, recommended for primary users), generally three types of code disturbances, such as JBuilder comes with (By default), can put private variables and The name of the method is replaced with garbled; slightly advanced, the public variables and methods can be replaced with garbled, usually the JAR and a script that you want to disrupt (used to control the retention section, otherwise your main program can't be executed Some of them don't have to garble with the keyword name, but directly with the keywords of Java, the reader may feel doubtful. In fact, this tool is to bypass the Java compiler, enter Class or JAR (not a source), after disturbing Output class or jar, of course, JVM is still executable! If these files use the general method, it is impossible to modify the modification and then compile with Javac or Jikes. The way to crack is first compiled with the anti-compilation software (all illegal variable name plus prefix) & #
