![]() |
|
|
|
#1
|
|||
|
|||
|
issue with .NET strong name remove
Hi,
I have hard time with a target that is writen in .NET it's a big application with alot of DLLs and i have manually done the strong name removing by using the reflexil plugin of reflector. I have also used "nt core" SNSRemover on one of the executables of the target. After that i have removed the signatured files, when i try to run the executable it crashes, and i get that it can't find some of the dll of the application. those DLL are within folders that are not in the same level of dir with the executable file. but if i copy all the dll files to the same dir of the executable then the file run normaly. does anyone knows why removing the public RSA keys will inpact the path of where to find the refrence files ? Regards, Labba. |
|
#2
|
|||
|
|||
|
Hi LaBBa,
I had a question on a similar .NET signing issue but mine was perhaps even more basic. I tried some removing the strongname signatures in the dll using this hxxp: // www.codeproject.com/KB/security/StrongNameRemove20.aspx Even though it didn't work for me, you may have better luck. Cheers |
|
#3
|
|||
|
|||
|
If dependent assemblies are in subfolders, I guess they are pointed by manifest with relative publickey token (that now you changed).
Try updating publickey token in manifest for dependent assemblies ... look here for more info: Code:
http://msdn.microsoft.com/en-us/library/0ash1ksb.aspx Code:
http://msdn.microsoft.com/en-us/library/4191fzwb.aspx Tony Last edited by tonyweb; 04-29-2011 at 02:32. Reason: more specific url |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Patching strong name .NET assembly | jjhsd | General Discussion | 9 | 01-30-2005 14:45 |