Some thoughts of Obfuscation
Obfuscation
However, unmanaged access to application source code can also pose material risks, including Intellectual Property (IP) theft, application vulnerability exposure and software piracy. For those organizations where these risks must be managed, there is really only one option-obfuscation. 3
Barak et al (2001) formalized the notion of obfuscation and demonstrated the existence of a (contrived) class of functions that cannot be obfuscated. In contrast, Canetti and Wee gave an obfuscator for a particular class of simple functions, called point functions, that output 1 on a single point (and output 0 everywhere else). Thus, it seemed completely possible that most functions of interest can be obfuscated, even though in principle general purpose obfuscation is impossible. 2
Learn more from Learn-About-swicki.eurekster.com/Obfuscation
While, as with native code, it is still theoretically feasible to infer the internal operation of an obfuscated executable, obfuscation makes this process much more time-consuming and difficult, and irreversibly destroys much of the high-level information about the original source form of your program. This transformation is done in a way which completely preserves the functionality of your product. 6
Obfuscated code is source code that is (perhaps intentionally) very hard to read and understand. Some languages are more prone to obfuscation than others. C, C++ and Perl are most often cited as easily obfuscatable languages. Macro preprocessors are often used to create hard to read code by masking the standard language syntax and grammar from the main body of code. The term shrouded code has also been used. 1
CodeMixUp’s Obfuscation is a quick and simple method of hiding your raw PHP source code from praying eyes. It will run on any platform that supports PHP and does not require any modules or further includes to run. 5
RetroGuard is a Java obfuscator, securing your code against decompilation and reverse engineering.RetroGuard bytecode obfuscation modifies the contents of your class files in such a way that their behaviour is unaffected, while minimizing the amount of information from the source code that is exposed. A side effect of RetroGuard obfuscation is that the class size is reduced, leading to faster download times for your Java products. 7
Obfuscating code to prevent reverse engineering is typically done to manage risks that stem from unauthorized access to source code. These risks include loss of intellectual property, ease of probing for application vulnerabilities and loss of revenue that can result when applications are reverse engineered, modified to circumvent metering or usage control and then recompiled. Obfuscating code is, therefore, also a compensating control to manage these risks. 4
Want more from Learn-About-swicki.eurekster.com/Obfuscation
