Home - Forums-.NET - Spices.Net - Spices.Obfuscator and strong names

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

Spices.Obfuscator and strong names
Link Posted: 11-Nov-2006 11:26
Hello,

I am currently evaluating the Spices.Obfuscator. Everything looks fantastic so far, however, there is one problem that I couldnt solve: My project uses .PFX files to sign the assemblies. When I give the PFX file as an input to Spices.Obfuscator, I always get an error message telling me that \"Signing XXX is failed\" without any other explanation. Using SNK files work without any problems, but PFX files (with password protection) does not work. Any helps regarding this issue will be greatly appreciated.

Best wishes,
Mustafa
Link Posted: 13-Nov-2006 00:25
In this case you can use one of the obfuscation events to use sn.exe (or another) utility to re-sign assembly after obfuscation:
1. Open your Spices.Project
2. Click Properties tab in opened document to activate current Spices.Project's properties.
3. Select and expand ObfuscationOptions property
4. Select AfterAssemblyGeneration obfuscation event to re-sign each assembly individually or AfterProjectGeneration to resign all assemblies of project at once.
5. Specify command line or batch file to re-sign assembly. AfterAssemblyGeneration obfuscation event provides filename as parameter for the batch files - you can use %1 as assembly filename to use in your batch file. AfterProjectGeneration provides Spices.Project filename as argument.

Aslo you can use MSBuild integration or create your own C#/VB.Net project that will implement custom obfuscation scenario - see the \\SDK folder for the samples.