Recommend few changes in ConfuserEx 1.6.0 which could make deobfuscation more difficult

[azzidoqsc]

Hello team,

I use ConfuserEx almost daily. It is such a nice project. I thank all of the contributors.
Now, I want to customize it a bit to make it incompatible with the deobfuscators on the internet.

Do you think it's enough to change this part from EncodePhase.cs ?

var key = new uint[0x10];
uint state = keySeed;
for (int i = 0; i < 0x10; i++) {
state ^= state >> 12;
state ^= state << 25;
state ^= state >> 27;
key[i] = state;
}

Currently, my application works perfectly with ConfuserEx set to Maximum, all protections added.
I appreciate your support.

[azzidoqsc]

I tried some forks that modify encryption/decryption of the constants but none of them are working. The ConfuserEx2_String_Decryptor can decrypt them.
Any suggestions please ?

[mkaring]

Altering the encryption keys will not help against the ConfuserEx2_String_Decryptor. This thing extracts and executes the actual decryption method. The decryption method must be able to decode the strings, otherwise the actual application wouldn't be able to access the strings.

The decryptor works based on the specific signatures of the string decryption method ConfuserEx uses. Meaning if you change that signature, the current version of the decryptor fill fail. But that can be easily worked around, by anyone who really wants to.

[azzidoqsc]

I appreciate your response.
Can you please help me with some hints on how can I change the signature correctly ? I'he tried to change the Initialize function slightly but the application does not start.
Any hints are more than welcomed.
I know there are commercial Obfuscators, but most of them present the same issue, there are plenty of de-obfuscators.
I prefer to customize my own ConfuserEx from time to time like you said, by changing the signature or some other sensitive parts.
I really appreciate your time, I have sent you an email too.
Looking for your response.