You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 27, 2019. It is now read-only.
I used the following line to obfuscate strings and array initializers (SI): [assembly: Obfuscation(Exclude = false, Feature = "constants(elements=SI)")]
Since array initialization causes problems with newer versions of MSBuild, I removed the 'I'-Element: [assembly: Obfuscation(Exclude = false, Feature = "constants(elements=S)")]
Unfortunately the obfuscation of array initializers is still happening. Example:
The following line var x = new[] { 1, 2, 3 };
will be obfuscated to int[] array = <Module>.<int[]>(2086960569u);
Could someone please tell me how to deactivate obfuscations like above?
Thanx
Thomas
The text was updated successfully, but these errors were encountered:
Hello. I also work a bit on protecting the protection. I'm trying to modify the basic protection strings (normal). I understand the encryption and decryption procedures. But not the principle of how the results from the confuser context are written into the assembly. I also do not know how mutation keys are being created. If you wanted to help me understand the principles. I will be glad. I will also share what I have come up with. Eddy ^
Hello,
I used the following line to obfuscate strings and array initializers (SI):
[assembly: Obfuscation(Exclude = false, Feature = "constants(elements=SI)")]
Since array initialization causes problems with newer versions of MSBuild, I removed the 'I'-Element:
[assembly: Obfuscation(Exclude = false, Feature = "constants(elements=S)")]
Unfortunately the obfuscation of array initializers is still happening.
Example:
The following line
var x = new[] { 1, 2, 3 };
will be obfuscated to
int[] array = <Module>.<int[]>(2086960569u);
Could someone please tell me how to deactivate obfuscations like above?
Thanx
Thomas
The text was updated successfully, but these errors were encountered: