Declare that the attack is only for learning and to better prevent the attack!
I have seen an occasional cracking attack recently. net controls, so it is also very novel, a hands-on test, but also really succeeded, can only sigh "a high foot, the magic of the feet", although there is encryption, but the experts made the tool, generally, cainiao (only a little bit familiar) can crack obfuscation of obfuscators. netCode.
This is the dundaschart, a good drawing control. I have read a lot of webpages and take it for winform 5.5 for vs2005 Enterprise Edition.
1. decompile ildasm dundaschartforwinform. dll and dump it to The. Il file. Then open it with notepad (ultredit) and remove. publickey to remove the strong signature.
2. Analyze the code because the generated il file contains some information, but it is not very nice. Here we provide a tool reflector to restore the. Il code very close.Source codeDegree, here, find the place where the watermark is displayed. In the chartpicture class, there is a painting () class, and the last section shows the watermark code, similar to the following code:
Bool a = true;
If (a) {// display the watermark code}
In this way, change LDC. i4.1 to IDC. i4.0 in the corresponding. Il code.
In this way, the watermark will never be displayed.
3. Finally, compile the Il file. here, by the way, an error occurs in the. Il file of re-assemble winform, prompting
Unkown_user, and then failure. Here I deleted the last section of the. Il file with the unkown_user attribute code segment, and then compiled it.
The compiled command ilasm/resource = Prog. Res/DLL Prog. Il
Note that the DLL is generated here, so the/DLL compilation switch must be added.
After adding it to the project, you need to re-compile it again.
In the routing operation, I can only use csc.exe to compile the project. If lc.exe is used, an error will occur.
In my case, a license file is also compiled into an EXE file (the license file), so lc.exe is used for processing. If we do not compile the license file into the target file (optional), then only the CSC compilation will be called and no errors will occur. But I don't know why ?? If you want to contact us via email: thomasliu83AtGmail.com
The following are the two files after the attack: (for learning only, I do not attach any responsibility)
Crack files in the network U disk address: http://Erich.ys168.com crack directory:
Chart for winform (v5.5) for vs.2005 DLL after cracking
Chart for Asp.net (v5.5) for vs.2005 after cracking DLL