Quote:
|
Originally Posted by newbie_cracker
I patched byte you've shown and sent patched DLL to my friend to test it.
This time .NET compiler said : "Invalid program" (or something like this).
May its because of joining your method and method of patching 80 at offset 102C.
|
It's exactly what you have to do. I checked it again and it works. Be carefully because the code I posted may be different from yours (you have to look at the position of the bytes), because I downloaded the latest version of the app for testing.
Quote:
|
Originally Posted by newbie_cracker
Tonight, I played with a simple file compiled with and without Strong Name. I noticed after compiling with KEY, 80 A0 and PublicKey are the major differences between two files. So my suggestion is : Patching whole PublicKey and 2 bytes before it to 00.
|
Probably it would work too, I didn't try it...
Quote:
|
Originally Posted by newbie_cracker
Present version of ILDASM (.NET SDK 1.1) crashes at decompiling time and the produced file is uncompilable. Do you decompile and recompile the mentioned dll successfully?
|
In my previous post I talked about future versions, try ILDASM from SDK 2.0 Beta...
PS: I suggest you to patch only the strong name infos at first. Test if the assembly works and after apply all other cracking patches.