In this series of tutorials we will be targeting .net applications,
Cracking is the art of removing or disabling copy protected coding from programs,
this manual will go into some detail on removing copy protection from programs.
If you feel offended by this, then I would suggest you stop here....
Tools:-
Before we begin, you will need certain tools, I use some of them, but this doesn't
Mean we will need them all Here, just make sure that you have them and try to
learn how to use them...
1. Reflector : .NET assembly Decompiler
Reflector is a class browser for .NET components. It allows browsing and
Searching the Meta data, IL instructions, resources and XML documentation
Stored in a .NET assembly.
.... (please read PDF)
The Opcodes:-
This is the most important point of cracking, as you know the .net application
Represent their program instruction in MSIL format which stands for Microsoft
Intermediate language, your source code is not translated to native machine-code
when you compile it in visual studio RAD, but it's translated to this format which
will later be compiled into native code by JIT compiler, JIT stands for just-in-time
Compiler, meaning that only certain parts of your programs will be translated into
Native code and executed on demand.
.... (please read PDF)
What lies beneath?
These are some of the obstacles that you will face when you crack any Assembly;
I will try to explain some of them here, for more information on any of them just
Google it.
1. Obfuscation:
It's the process of changing the method and classes names to nonreadable
Characters to make harder for us to find the "IsLicensed" function, yes;
It can make the job harder for you but believe me it's not that hard to
trace
2. Encoded Strings:
Entire encoded stream as a binary .net resource, and whenever some
string is
Needed, A function is called to get that string from encoded stream and
It will return the original string, the point that makes this technique weak
Is that it has to be fast in decoding to keep the program running fast
3. Strong Name signature:
This is a primitive technique used to protect .net assemblies from any
Tampering or modification after the assembly is released to the public.
When you start an exe application built with .net, it will be checked
By the run-time for string name signature, if it exists then the digital
Signature is verified, if verification fails then this means that the
Assembly has been modified after it was released and the runtime
Will refuse to load it!
.... (please read PDF)
DOWNLOAD PDF dark .NET cracking no.1 Basic
http://adf.ly/KxTTq
DOWNLOAD .NET Reflector 8.0 + Addin for crack
http://adf.ly/KxTdm
DOWNLOAD .NET PE Scanner
http://adf.ly/KxTiq
Creadit Ebook to Kurapica
