ildasm

  • Thread starter Thread starter JLW
  • Start date Start date
J

JLW

Now, all these companies are making products that can crash ildasm, thus
preventing assemblies from being disassembled. Is there specific code I can
add to my assembly to do this? Also, I read about a /owner option for ilasm
that appears to only have been in the BETA version of the framework. Why
was this not included? It seems it would've provided some level of ildasm
protection.

Thanks,
JLW
 
It was removed as it only stopped ildasm from viewing. As for how you can do
it, add to the IL. That is how the obfuscators do this, by adding commands
ildasm cannot understand, but do not affect the code at runtime.

Most obfuscators work by either adding garbage or naming a bunch of things
by the same name. When IL is compiled to machine code, it can tell whether
you are calling the integer i or the long i or the string i. It is much
harder for a human to decipher, if he can decompile in the first place.

NOTE that those that simply crash ildasm do not stop you, the dev, from
creating your own decompiler, so you need more strength than merely a ildasm
crasher.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************
 
Back
Top