I have great news to share. We were able to identify and leverage some useful properties of a partially homomorphic cryptosystem to achieve a considerably better obfuscation results. How much better? Up to the point where parts of a program remain totally unobservable unless they hit the actual execution path.…
Eazfuscator.NET 2018.2 brings seamless integration with Unity.
Eazfuscator.NET now officially supports .NET Core and .NET Standard technologies.
C# 7 and Visual Basic 15 introduced the notion of value tuples. The concept is similar to what you may find in System.Tuple but with two important distinctions:
What if you had a personal assistant that could guide you through particulars of obfuscation?
Wait no more. Eazfuscator.NET 5.3 introduces a deeper Visual Studio integration that improves your productivity when it comes to obfuscation directives and configuration:
Eazfuscator.NET 5.3 has been released just a few hours ago, and it brings a particularly useful feature: resource sanitization.
Say you have the following XML file as an embedded resource of your .NET assembly:
<!--
Please thoroughly consult
https://www.dropbox.com/s/jv1my3n1e0d/GrandPlanOfThings.pdf?dl=0
before making a change.
-->
<lisp>
(define one? (λ (z) (= z 1)))
...
</lisp>