|
|
|
|
#1
01-24-2005, 22:50
|
|||
|
|||
|
Thank you for your reply.
I have checked this article. However I don't think it's gonna to be helpful, as the program has used some obfuscator. I wish i could patching the binary file without recompiling it from MSIL. I just found a solution to problem a). So b) will be the only remaining problem. after I patched the file and tried to resign them with my own key pair, the application doesn't run any more. U_U Actually i think this problem is quite generally. There will be more and more applications written in .NET in the future, and strong name assemblies will be one of the most common things to be implemented as part of software's secutires. 
|
|
#2
01-24-2005, 23:15
|
|||
|
|||
|
Hi,
If you're working with a Windows app the easiest way to solve b) is fooling the CLR patching the Strong Name Signature size from 80h to 00h. In this way the CLR thinks that the assembly is not strongnamed. The offset for this byte change from assembly to assembly but usually you can find it at the beginning of the file (from 200h to 300h)... You can find useful infos here... h**p://www.woodmann.net/forum/showthread.php?threadid=4389 Regards, SystemeD
|
 |
| Thread Tools | |
| Display Modes | |
|
|
Hybrid Mode
