Skip to content

ConfuserEx 1.4.0
Compare
Choose a tag to compare
@mkaring mkaring released this 06 Jul 20:27
v1.4.0
This tag was signed with the committer’s verified signature.
mkaring Martin Karing
GPG key ID: 3C03D13B7A32D34A
Learn about vigilant mode.
1fac295

⚠️ Severe known issue

There is a severe issue related to the control flow obfuscation. The protection will break the runtime behavior of complex methods. At this point is recommended to stick to the previous release until a fixed version is released.

The issue is tracked here: #162

🚀 New features

  • Support for enhanced strong name signing (#118)
    Enhanced strong name signing is now fully supported in the CLI and GUI.
    Thanks to @justremotephone for the implementation.
  • New hardening protection added. (#129 #135)
    This new protection enhances the code of the other protections to make common methods to read ConfuserEx protected assemblies significantly more difficult.

🐛 Bugfixes

  • Fixed buttons in ConfuserEx UI that were not switching the enabled and disabled state properly. (#99)
  • Fixed renaming of protected properties and events. (#103)
    These members are not renamed anymore, in case they are visible outside of the assembly.
  • Fixed renaming of XAML files, in case multiple WPF assemblies are protected as once. (#105)
  • Fixed output handling for MSBuild integration. Replacing the output assemblies now works properly (#110)
  • Fixed watermark handling in case the watermark assembly is already present. This usually happens in case an assembly is obfuscated twice. (#116)
  • Tracing the used arguments of a method now works significantly better in case dup instructions are present. (#127 #152)
  • Fixed rename handling in WPF property paths. The properties were renamed, but the new names did not get transferred to the BAML. (#137)
  • Fixed error in control flow obfuscation that turned any loop into a infinite loop by chance (#153)
  • Fixed renaming of inherited properties and events (#123 #154)
    Properties and events now share their name across the inheritance structure, to allow the reflection handling of those properties to work properly. This entails that properties are not getting renamed, in case they are implementing a property that is not subject to protection.
    Thanks to @wmjordan for the support figuring this one out.

🎉 Improvements

  • Support for disabling the watermark. (#115)
    Some people really dislike the watermark, so there is now a way to disable it. The watermark is now a "protection" that is enabled by default. This protection can be removed in a rule covering the module to remove the watermark.
  • Splitting up release packages (#146 #157)
    The packages for ConfuserEx are now split into 3 deployments.
    • ConfuserEx-CLI.zip contains only the CLI executable and it's dependencies
    • ConfuserEx-GUI.zip contains only the GUI executable and it's dependencies
    • ConfuserEx.zip contains everything

🙏 Thank you

Thank you to everyone reporting issues, creating pull-requests and in general using ConfuserEx. Special thanks to @ElektroKill and @KvanTTT for the contributions, ideas and reviews.

Assets 6
Loading