Hello Friends

     i want your feedback which is the best obfuscator to prevent .net application again reverse engineering.

 

Thanks 

mov eax,null

Use CONFUSEREX Moded.....

but i think you can not prevent reverse engineering.

Edited March 9, 20169 yr by HAMID

The open source obfuscators can not be trusted.

all obfuscators can be crack.....there are no any protection....

1 hour ago, Perplex said:

The open source obfuscators can not be trusted.

Because they're open source? One advantage of an open source obfuscator is that you can modify the algorithms and add other stuff to prevent tools from working.

Did you know that there are more deobfuscators for commercial obfuscators than for open source obfuscators?

There's no obfuscator that offers any real protection, they just slow down the inevitable: your competitor will copy your code or someone will crack your app.

Edited March 9, 20169 yr by 0xd4d

On 2016/3/10 at 0:43 AM, 0xd4d said:

Because they're open source? One advantage of an open source obfuscator is that you can modify the algorithms and add other stuff to prevent tools from working.

Did you know that there are more deobfuscators for commercial obfuscators than for open source obfuscators?

There's no obfuscator that offers any real protection, they just slow down the inevitable: your competitor will copy your code or someone will crack your app.

I can't agree with you any more

DNGuard HVM last version and full version (not trial) is the best.
Agile .net is also a good due to msil virtualization, msil encryption CAN be defeated (I think).
 

Think about it, do we need to use a VM to protect a VM ?

How about applications that require every cycle of CPU power ?

What you can do at best is to obfuscate the names and not even the control flow, other protection features

will make your application slower.

 

On 9/20/2016 at 11:42 AM, Kurapica said:

will make your application slower.

This is a good argument if you want to protect your critical algorithms, but most software will be waiting for files/network 99% of the time for which that 100x overhead doesn't matter much, just keep it under 100ms observable reaction time and performance is not a big concern, also the JIT that .NET uses has considerable overhead and shouldn't be used for performance critical tasks anyway