C++ Mixed Mode

.NET obfuscator and automated error reporting

Moderators: Luke Jefferson, Alex.Davies, melvyn.harbour

C++ Mixed Mode

Postby omheien » Tue Dec 07, 2010 3:07 pm

Hi all
I have a C++ DLL holding two exported procedures that lets me load the library in our Win32 application created in Clarion for Windows (Not .NET)
Tis C++ library allso holds some managed code that lets me do calls from my Win32 applications into the .NET world.

I'm using IJW to acomplish this task.

I tryed the evaluate version of SA to see if I could obfuscate my Visual Studio solution, but it stopped on my C++ project saying that Mixed Mode is not supported. I then obfuscated just the C# projects and that worked well. But then I assume that my C++ DLL not longer can access the C# projects.

Am I right or can this be done?

If not, I must look for an other obfuscator.

regards
Ole
omheien
 
Posts: 18
Joined: Tue Dec 07, 2010 2:07 pm
Location: Norway

Postby Brian Donahue » Wed Dec 08, 2010 4:56 pm

Sorry, Ole. you can't use the current or previous versions of SmartAssembly to protect assemblies that have a mix of managed and unmanaged code.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am

??? Does this mean that SA is not an option for me at all?

Postby omheien » Thu Dec 09, 2010 7:51 am

I mean, since I can ObFuscate all the C# modules, is it not possible to decorate a class or method in my C# project that tells the obfuscator NOT to obfuscate? Because this would let the C++ code call the C# library. This is as fas as I can see then way many other obfuscators do it. Problem is that there are only two obfuscators that prevent hackers from seeing the code inside the methods, at least this is what I have found testing the one I found. And the other ObFuscator that manage this is DotFuscator from PreEmptive. Problem is that they wanted €2500 for the product, and that was including a 50% discount, which means the product actually costs €5000. A rather amazing prize for an obfuscator
omheien
 
Posts: 18
Joined: Tue Dec 07, 2010 2:07 pm
Location: Norway

Postby Brian Donahue » Thu Dec 09, 2010 12:08 pm

Hi Ole,

I'm guessing it's because SA gets a lot of the information about types from the metadata to work out how to obfuscate them and unmanaged code does not have this information available in the assembly.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am


Return to SmartAssembly 5

Who is online

Users browsing this forum: No registered users and 0 guests