Re: obfuscation & reflection

From: CSharped (csharped_at_yahoo.com)
Date: 01/06/05 

Date: 6 Jan 2005 08:59:01 -0800

MrNobody wrote:
> How would you handle this situation:
>
> I have a series of classes which are to be later loaded using
reflection:
> but the class to be used can vary depending on strings from a text
file. So
> this text file will have some of these class names in it to govern
which
> class gets used.
>
> Now, I want to obfuscate as much of my program as I can, though if I
> obfuscate everything it won't work anymore because those class names
in the
> text file no longer match anything in my assembly. These classes in
> particular have no sensitive information, so it would be fine to
leave them
> un-obfuscated.
>
> But what's the easiaest way to accomplish this? Put them in their own

> namespace and tell the obfuscator to ignore them? Or put them in
their own
> assembly like a dll that gets referenced by my app? What would you
do?

I don't know what obfuscator are you using or planning to use, but if
the code you have just finished is complete, you shouldn't change the
code for the sake of the obfuscator. It should be the other way around.

For Dotfuscator, you can single out the classes you want excluded from
renaming by using regular expressions or by certain characteristics
such as access modifiers.

Any other documentation on Dotfuscator can be found here:
http://www.preemptive.com/downloads/Documentation.html

Relevant Pages

  • Re: Keeps getting exception in dotfuscator output
    ... The exception I got was a file not found exception or something like ... So now I can obfuscate my app. ... When giving the release version as input to dotfuscator it says this ... use the "rename" feature. ...
    (microsoft.public.dotnet.framework)
  • Re: Protect IL Code
    ... "Alek Davis" wrote: ... then it can be configured to obfuscate only private and internal ... If DotFuscator ... >> We can configure obfuscator tool with a list of exception names that the ...
    (microsoft.public.dotnet.security)
  • RE: .NET and keeping my source code to myself...
    ... I understand that you need to obfuscate your assembly to ... Visual Studio .NET 2003 has provided us with a tool called Dotfuscator. ... Dotfuscator is an obfuscator for .NET assemblies. ... smaller and faster .NET applications. ...
    (microsoft.public.dotnet.general)
  • Re: Dotfuscating Part of an Application
    ... next best thing would be to dotfuscate the DLLs that are part of the ... If you're using the Dotfuscator Community Edition that ships with VStudio, ... you'll need to obfuscate all assemblies together as a group. ... obfuscating anything in the dependent assemblies. ...
    (microsoft.public.dotnet.security)
  • RE: Winforms and reverse engineering
    ... To *obfuscate* code are some tools like ... Dotfuscator it cames a ... Prev by Date: ...
    (microsoft.public.dotnet.languages.vc)