Comments
4 comments
-
The only defence is to ensure that all protections are added and added at their highest level.
-
Chris.Allen wrote:The only defence is to ensure that all protections are added and added at their highest level.
Even with those settings, our program (130k+ lines of code) is easily reversed with the vital parts exposed!
Within a minute I was able to decipher internal passwords, logic and it resembled my code quite a bit again. -
same behavior here!
sa 6.8.
One solution must be provided by redgate. -
any news about this?
I will not be able to renew my subscription if redgate does not provide a solution to this problem.
Add comment
Please sign in to leave a comment.
I used SmartAssembly 6.8 against our largest .NET assembly with 200,000+ lines of code with the highest levels of obfuscation available, and when inspected in .NET Reflector, the implementation code is not visible at all.
I then ran de4dot 2.03 against it, and I can now view the implementation in the cleaned assembly file using .NET Reflector, and the code is extremely close to the actual source code, taking the auto-generated compiler stuff into account.
This took me about 5 minutes and required very little technical knowledge - download, extract a zip, drag and drop a file onto an EXE, done.
Is there anything that can be done to block the effectiveness of this program?