Anti ILDASM option does not work any more

[Wookeun]

Dear all,

We used "Anti ILDASM/Suppress Decompilation" option to protect our
assemblies, but last week we found out that Reflector is able to
decompile our assemblies. Just to validate the problem, we crated a
simple dll (hello world type of dll) in Visual Studio and protected it
with "Anti ILDASM" option. The dll was decompiled by Reflector without
any problem.

Could you possibly help me to solve this problem?

OS: Windows 7 Ultimate 64-bit
Version of Reactor: v4.4.0.0
License: It says "Full version"

Best regards,
Wookeun

[sali98]

You can forget the "Anti ILDASM/Suppress Decompilation", a lot of
tools can open it anyway,
even with the ILDASM, if you manually erased attribute settings from
the dll binary, it can also
be opened.

[Glen Harvy]

On 30/03/2012 4:31 PM, sali98 wrote:
> You can forget the "Anti ILDASM/Suppress Decompilation", a lot of
> tools can open it anyway,

I can't help but comment that your comment will apply to all
"protection" systems.

I really am amazed that *anyone* actually expects that 'obfuscating'
their .Net assembly will stop any serious hackers from discovering your
code.

[Sa Li]

I absolutely agree to your point! Though our product also obfuscated and encrypted, while I don't think it would actually prevent bad things from happening. And due to some bugs of those tools, we have got some troubles to troubleshoot the problems.

--
You received this message because you are subscribed to the Google Groups ".Net Reactor Support" group.
To post to this group, send email to net-reactor-support@googlegroups.com.
To unsubscribe from this group, send email to net-reactor-support+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/net-reactor-support?hl=en.