Symbol Renaming
⏩Performance: None 🔐Potency: High 🧠Resilience: High
Understanding the protection
Symbol renaming is a critical obfuscation technique, the names of classes, methods, properties, fields, method parameters, and locals are replaced with randomly generated names.
Before Obfuscation:
After Obfuscation:
Tuning the protection for best performance
There are three different modes for this protection, all of them serve the same purpose, erasing the original names of your application, however, depending on the aim that you want to achieve with the obfuscation, you should opt which one suits you better.
Minify
When choosing this option, the names of your application are removed to ensure that your application size is the smallest possible, when erasing the data is not possible, the obfuscator will use single characters as names for the member being renamed.
Before:
After:
Encrypted
When choosing this option, the names of your application are encrypted with a private key of your preference, this makes it possible for you to decode stacktraces provided by customers and easily debug your application after obfuscation.
Before:
After:
You should always safeguard the key used for obfuscation, exposing it to the public could compromise the encrypted names. ❗
Default
When choosing this option, the names of your application become incredibly difficult to read both to humans and machines, leading to the crash of reverse engineering applications in some scenarios.
Before:
After:
This mode delivers the most confusing obfuscation output to human attackers, however, the names given by this method tend to be bigger than the original name, therefore the size of your application can become significantly bigger after using this method.
Last updated