Home - Forums-.NET - Spices.Net - Confusing verification errors

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

Confusing verification errors
Link Posted: 05-Apr-2007 11:06
I'm evaluating your software to be used for our product. When verifying an obfuscated assembly, I'm getting a whole lot of errors like the following:

[MD] Error: Implementation Map has invalid calling convention 1024, rid:0x0001.
[MD] Error: Warning: Item, token=0x060004cf (field,method) has invalid Implementation Map.


This starts with rid 0x0001 and goes up through 0x041a occasionally skipping some. Despite these several hundred errors some basic testing of the obfuscated assembly doesn't seem to show any problems.  However I couldn't find anything in the documentation to explain what these errors actually mean.

What do these errors actually mean and should I be concerned about them?
Link Posted: 06-Apr-2007 04:18
Could you send this assembly to us (to , please zip your assembly and change extension of archive to .zap or .zip.txt to proceed our mail hosting requirements for attachments) for analysis and to more precisely answer your question.
You can try to verify original assembly, if that warnings produced by verification of original assembly - don't worry, this is incorrect work of verification procedure. Your assembly helps us to quickly fix this problem.
Link Posted: 06-Apr-2007 04:23
This does happen on the original assembly as well.  I'm not sure I can send you the assembly though.  We will likely be buying the product in the next week or so, after which I will send a fully obfuscated assembly that shows the verification errors.

Thanks for the quick response.
Link Posted: 06-Apr-2007 04:28
Yes, send us obfuscated assembly - it is enough for analysis.
We're preparing nearest update of Spices.Net and it would be good if we fix this problem to this update.