Crypto Obfuscator for .Net v2013 R2 Adds Support for Code Masking and Constant Field Removal
The recently released Crypto Obfuscator for .Net v2013 R2 includes support for code masking and constant field removal. With the help of code masking, the commonly used code patterns such as using, foreach, is/as, unboxing, creation of arrays/structures, typeof, overloaded operators and string concatenations are replaced by method calls, which is not easy to understand as the original code pattern.
The latest release provides an ability to remove the value associated with all constant fields, that are defined using const keyword in C# and Visual Basic .NET, which according to the product team will provide extra security in addition to optimization.
Crypto Obfuscator for .Net v2013 R2 enables you to apply rules based on the attribute applied to a symbol and enclosing type of a member. It also includes an ability to fields/properties/methods/events by type. Moreover, environment variables can be used inside the BuildID, which in turn will be able to make use of a special environment variable of the form %assemblyname_version%.
The recent release enables you to copy a single warning to the clipboard with the ability to make use of watermarks in environment variables in addition to obfuscate and execute obfuscated assemblies using F5 and F7 shortcut keys. It also provides support for a scenario where a portable class library is referenced by the assembly being obfuscated including support for Visual Studio 2012.
Moreover, you can also explicitly specify an assembly added to the obfuscator project as a WinRT assembly including the ability to specify certificate file used for Authenticode via command-line. You can also filter running processes data from exception reports and specify pfx password via command-line in addition to support for deobfuscated stack traces
generated by Unity3D.
Crypto Obfuscator for .Net v2013 R2 has been updated to provide Linux and Mono support for automatic exception reporting service. The email notifications generated using the reporting service include project name, which will be useful if the same service is being used for multiple projects. It also includes several improvements, changes and bug fixes.
How Can We Use Our Creative Power and Technological Opportunity to Address the Challenges of the 21st Century?
Gyorgyi Galik Feb 26, 2015