LogicNP Software
Crypto Obfuscator For .Net v2013 R2 - New Code Masking And Const Field Removal Obfuscation Settings

We are pleased to announce the release and immediately availability of a new build of v2013 R2 of Crypto Obfuscator for .Net, with a brand new Code Masking and Constant Field Removal features:

Code Masking

This setting masks some commonly used code patterns like using, foreach, is/as, unboxing, creation of arrays/structures, typeof, overloaded operators, string concatenations and more. These code patterns are replaced by method calls which do the exact same thing, but whose purpose is not as easy to understand as the original code pattern.

Remove Constant Field Values

When this setting is specified, Crypto Obfuscator will remove the value associated with all constant fields. Constant fields are defined using const in C# and VB.Net. The constant value specified in source code is not required after compilation and so it can be safely removed. This provides extra security as well as optimization.

General Product Information : http://www.ssware.com/cryptoobfuscator/obfuscator-net.htm

Download: http://www.ssware.com/cryptoobfuscator/download.htm

What's New In v2013 R2

The following is the list of changes accumulated over the builds made since the previous version:

• NEW: Code Masking Obfuscation - Code Masking masks some commonly used code patterns like using, foreach, is/as, unboxing, creation of arrays/structures, typeof, overloaded operators, string concatenations and more. These code patterns are replaced by method calls which do the exact same thing, but whose purpose is not as easy to understand as the original code pattern.
• NEW: Remove Constant Field Values obfuscation.
• NEW: Obfuscation rules can now be applied based on the attribute applied to a symbol, attribute applied to enclosing(declaring) type of a member, the assembly which contains the symbol or the attribute applied to the assembly containing the symbol.
• NEW: Added ability to exclude fields/properties/methods/events by type.
• NEW: Environment variables can now be used inside the BuildID.
• NEW: BuildID can now use a special environment variable of the form %assemblyname_version% (example: %MainApp_version%). This allows you to specify as the build id, the version of any assembly added to your obfuscation project.
• NEW: It is now possible to copy a single warning to the clipboard by right-clicking on it.
• NEW: Ability to determine (from within application using a simply property) whether the obfuscated or unobfuscated version of your application is running.
• NEW: Environment variables can now be used in watermarks.
• NEW: It is now possible to obfuscate and execute obfuscated assemblies using shortcut keys (F5 and F7 respectively).
• NEW: Added support for scenario where a Portable Class Library is referenced by the assembly being obfuscated.
• NEW: Ability to explicitly specify an assembly added to the obfuscator project as a WinRT assembly.
• NEW: Added ability to specify certificate file used for Authenticode signing of obfuscated assemblies and corresponding password via command-line.
• NEW: Ability to exclude/filter running processes data from exception reports.
• NEW: Added ability to specify pfx password via command-line.
• NEW: Added support for deobfuscated stack traces generated by Unity3D.
• NEW: Automatic Exception Reporting Service now supports Linux/Mono.
• NEW: Exception Reporting Service email notifications can now include the project name, which is helpful if the same service is being used for multiple projects.
• NEW: The Crypto Obfuscator Visual Studio Addin now supports Visual Studio 2012
• IMPROVED: Greatly improved speed of obfuscation rule matching reduces the time taken for obfuscation a bit.
• IMPROVED: Visual Studio Integration Wizard now shows a descriptive error message if it does not find any suitable project configuration for integration.
• IMPROVED: New warnings added.
• Minor UI improvements.
• IMPROVED: Members of enums which are marked as Serializable are not renamed.
• IMPROVED: Added some minor details to the log.
• IMPROVED: During assembly resolution, Crypto Obfuscator now automatically searches the folders of "Additional Assemblies" specified in the obfuscation project.
• Improved documentation.
• IMPROVED: Minor logging improvements.
• IMPROVED: Visual Studio Project Integrator Wizard now supports .sln and .proj files containing special escape characters.
• IMPROVED: Improved support for control flow obfuscation for certain assemblies produced by the C++/CLI compiler.
• IMPROVED: Improved support for certain PDB files produced for C++/CLI assemblies.
• IMPROVED: Improved support for boxed enums in attributes (both fixed and named params), when the enums are defined in another assembly.
• IMPROVED: The namespace and typename of an enum is renamed even of its members are auto-excluded because of a call to ToString.
• IMPROVED: More helpful error messages if obfuscation errors occur.
• NEW: Added support for "Filter Data" in Exception Reports.
• IMPROVED: Improved usability of the Crypto Obfuscator Visual Studio Add-In. The menu command added by the add-in now changes text - "Enable Crypto Obfuscator" or "Disable Crypto Obfuscator" - depending on whether Crypto Obfuscator is enabled or disabled.
• IMPROVED: Modified MSBuild Integration Wizard XML output in .csproj/.vbproj files to make it easier to integrate shared projects in multiple solutions.
• IMPROVED: Improved reporting of errors/exceptions that occur in the exception reporting service back to the Crypto Obfuscator UI.
• IMPROVED: Additional logging when Crypto Obfuscator is run as part of MSBuild integration.
• CHANGE: Locally saved exception report files are now deleted when the corresponding entry is deleted from the "Exception Viewer Dialog"
• CHANGE: Improved logging improvements.
• CHANGE: Better resize support for Visual Studio Project Integration Wizard.
• CHANGE: Some new additional info is logged if errors occur during obfuscation.
• FIX: Exclusions for features other then "renaming" (like "controlflow","encryptmethod", etc) did not work when a custom ObfuscationAttribute (not "System.Reflection.Obfuscation") was used.
• FIX: Automatic Exception Handling did not work for exe assemblies if they referenced the system.web assembly.

• FIX: The WebSiteExceptionReporting sample did not save exception reports to the correct folder, so they could not be downloaded from the Crypto Obfuscator UI.
• FIX: Fixed layout issues with Visual Studio Project Integration Wizard, which causes the "Browse For Solution" button to remain out of view.
• FIX: "Anti-Tamper Protection" did not work correctly when running under Mono on Linux.
• FIX: Obfuscated program could not be verified if "Method Call Hiding" was ON, and code created a generic multi-dimensional array.
• FIX: Regression bug in Automatic Exception Handling for Silverlight Assemblies - exceptions were not being handled in come circumstances.
• FIX: Obfuscation is not aborted if Crypto Obfuscator is unable to delete pdb file.
• FIX: Remove Constant Field Values setting not saved to .obproj file.

For build-wise version history, goto http://www.ssware.com/cryptoobfuscator/versionsnet.htm

Upgrade Information

v2013 R2 is a free upgrade for customers with an active Support And Upgrade Subscription. Your v2012, v2012 R2 and v2013 license will continue to work with this new build.

v2013 R2 is a paid upgrade for customers whose Support And Upgrade Subscription has expired. To upgrade to v2013 R2, goto http://www.ssware.com/upgrade.htm

To start using v2013 R2, uninstall your existing installation of Crypto Obfuscator, download the updated installation from http://www.ssware.com/cryptoobfuscator/download.htm and reinstall.