0

I am NOT looking to make my application 99% safe, nor my goal is to prevent a a determined reverse-engineer to disassemble it, but simply is to protect my source code from lambda user with little knowledge having a powerful de-compiler like REflcator or dotPeek between his hand to literally get the whole source-code project from the executable. It is surprising how much it is easy and efficient.

I am not looking for obfuscation only but packing the code in a wrapper effectively or any other way that makes the de-compilers task very hard at the first place.

From Prevent Decompiling, I have tried to convert it to native code using Ngen.exe but it was not working. Also tried obfuscator which was even breaking the app sometimes.

Then I tried Themida and .Net Reactor trial versions, both are very satisfying unfortunately they are not free.

which brings me to the idea to write my own wrapper:

  1. How the two softwares above works? ie: are there any resources/documentations about known techniques used for packing and protecting against de-compiling, to server me as a guidance to start ?
  2. Will writing an effective packer & obfuscator for .net (more specifically wpf if it does matter) executable makes it as hard to disassemble as a C or C++ one?

Note: Question already posted in Stackoverflow but not sure it was the correct place: https://stackoverflow.com/questions/61637278/what-are-the-known-techniques-used-by-wrappers-and-obfuscators-to-protect-agains

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.