Home - Forums-.NET - Spices.Net - command line eval mode limitation?

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
command line eval mode limitation?
Link Posted: 25-Oct-2006 14:01
djohnson avatar
djohnson
Total Posts:0
Joined:4/26/2024
I notice when trying to obfuscate, using the command line version, via a post build event, the switches I pass in (i.e. NIMA%94) still obfuscates internal fields.

is this a limitation in functionality of the evaluation license? (not having granular functionality control?) or is it a limitation of the obfuscator?

specifically, my assembly uses reflection and serialization and I am trying to obfuscate it with your console obfuscator to get something that will still run, the only way I have done this with other obfuscators is to disable field obfuscation. which does not seem to be an option with the evaluation license.

Please advice.
David Johnson
Link Posted: 25-Oct-2006 23:03
NineRays avatar
NineRays
Total Posts:0
Joined:4/26/2024
specifically, my assembly uses reflection and serialization and I am trying to obfuscate it with your console obfuscator to get something that will still run, the only way I have done this with other obfuscators is to disable field obfuscation. which does not seem to be an option with the evaluation license.


But if some classes used in serialization/reflection - these classes should be public.
Can you send us this assembly for analysis, to help you create effective obfuscation config and to give recommendations.
We guarantee that your software will used only for tests/analysis, doesn't transferred to any 3rd party and deleted when tests/analysis will finished.
Please send your assembly to
Link Posted: 26-Oct-2006 02:29
djohnson avatar
djohnson
Total Posts:0
Joined:4/26/2024
can you confirm whether or not the evaluation license is limiting the functionality of the obfuscation?
I notice when trying to obfuscate, using the command line version, via a post build event, the switches I pass in (i.e. NIMA%94) still obfuscates internal fields.

is this a limitation in functionality of the evaluation license? (not having granular functionality control?) or is it a limitation of the obfuscator?

Link Posted: 26-Oct-2006 03:45
NineRays avatar
NineRays
Total Posts:0
Joined:4/26/2024
The latest version has no fucntionality limits, only mark assembly as \"obfuscated by evaluation version\", but the internal members for obfuscator - is private members (visible only in the current assembly) that should be obfuscated.
If you need to leave private members from obfuscation, it would be best to use some of exclusion ways -
1. Using ExclusionPatterns
2. Excluding manually in the Spices.Net AssemblyBrowser
3. Declarative exclusion by using NotObfuscateAttribute or NotObfuscateMembersAttribute (analogue of exclusion patterns).

We can implement automatic exclusion of internal members but please send us a sample that describe problem.
Share:

Company  |  Privacy  |  Legal Information

© 1999-2024 9Rays.Net. All rights reserved.