Code Obfuscator, De-compilation ToolThe purpose of the code obfuscator was to prevent attackers from analyzing the code logic through reverse engineering by converting the source code into an incomprehensible form, such as code disorder, using obscure names to renamed classes, fields, and methods. It was to prevent the code from being reverse-cracked instead of being reverse-compiled. Common code obfuscators include R8 (based on DexGuard and also suitable for Java applications) for reducing and obfuscating Android applications, as well as ProGuard, which is popular in Java. ProGuard can compress and optimize your code, remove useless classes, fields, methods, attributes, and comments, and use short, meaningless names to renamed classes, methods, and attributes. There are also Allatori Java Obfuscator, VirboxProtector, ipaguard, DashO, Zelix KlassMaster, RetroGuard, and others that can be used for code obfuscating.
If you want to debuff the obfuscated code (for example, when the obfuscated code prints stack information, the method name is not recognized), in the case of ProGuard obfuscated, it will output a mapping. txy file that contains the original class, method, and field names that have been converted to obfuscated names. You can use the retrace.bat script (Window) or the retrace.sh script (linux.macosx.com) to restore the obfuscated stack trace information into readable information.
Common deconstruction tools could restore the compiled code to a certain degree of readable source code, such as a deconstruction tool for Java bytecode, but this was the opposite of the function of a code obfuscator. The reason why I didn't mention a specific deconstruction tool here is because the reference materials didn't focus on deconstruction tools.
<a href="/?from=ask_words" style="color:red" target="_blank">Read more exciting novels for free</a>
C'est partie pour une nouvelle partie des critique sans sens de la journée pour atteindre les 140 caractère demandé. Et c'est toujours long et fastidieux ? non ?