Home - Forums-.NET - Spices.Net - [Obfuscator] Strong named assemblies re-signing

Spices.Net

NET code security, tools to protect, obfuscate, tamper defense, code and data safety, recover, convert, optimize, explore, browse and analyze .Net software.

This forum related to following products: Spices.Net Suite, Spices.Net Obfuscator, Spices.Net Decompiler

[Obfuscator] Strong named assemblies re-signing
Link Posted: 17-May-2007 16:41
Is it possible to re-sign assembly using key, which is not equal to that one which was originally used to sign assembly?
I'm afraid not, because in this case I get \"strong name verification failed\" exception, when starting my program.
Probably, obfuscator doesn't fix references to re-signed assembly?
Link Posted: 18-May-2007 06:45
It isn't a bug, it is a feature - to prevent assemblies from anauthorized use. You should use original strong name key file to resign your assemblies.
Link Posted: 18-May-2007 16:28
[quote="NineRays"]It isn't a bug, it is a feature - to prevent assemblies from anauthorized use. You should use original strong name key file to resign your assemblies.

In this case, you'd better add an appopriate error message during obfuscation process. That's not good, when obfuscator silently breaks the program down.
Link Posted: 18-May-2007 17:10
Thanks for the suggestion, we'll add strong name check to verification procedure.