Re: Secure exe/dll

From: Aman (akg_at_infores.com)
Date: 05/23/03 

Date: Fri, 23 May 2003 11:31:13 -0700

Shawn,
Thanks, I did not know about the first option but I've
done the second option with COM.
Thanks again.
Aman
>-----Original Message-----
>Aman,
>
> Since .Net assemblies contain both IL code and
metadata describing that
>code, it is easier for people to disassemble your
assembly and figure out
>how it works than it would be if you had native code.
Depending on the
>level of secrecy you want, you could try two techniques.
You can use a code
>obfuscator to scramble your assembly and make it more
difficult to
>understand. Visual Studio 2003 ships with Dotfuscator
Community Edition
>(which you can also download for free at
>http://www.preemptive.com/dotfuscator/dotcomdld.html ).
Another technique
>would be to take your sensative algorithms and implement
them in a native
>DLL. This would make them more difficult to disassemble
and figure out, and
>you could P/Invoke into them or use COM Interop.
>
>-Shawn
>
>"Aman" <akg@infores.com> wrote in message
>news:0fb801c32143$29c52fe0$a101280a@phx.gbl...
>> I've a quick question regarding how to prevent my
>> customers from seeing my code using MSIL Disassembler
>> (Ildasm.exe) from my EXE/DLL's. If I use the Ildasm.exe
>> and open a C#.NET EXE/DLL I can see the source code and
I
>> don't want anyone seeing the code that generated the
>> DLL/EXE since it contains some complex and secret code.
>> Does anyone have any idea how to creat a secure .NET
>> exe/dll that cannot be disassambled by Ildasm.exe or
other
>> tools?
>> Thanks,a
>>
>>
>
>
>.
>

Relevant Pages

  • RE: Vista Applications: Authenticode vs Signing Assembly with StrongNa
    ... which let runtime correctly identify different .net assemblies. ... Microsoft MSDN Online Support Lead ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.general)
  • Re: Protecting .NET assemblies (runtime)
    ... you can try to do your best - like checking the SN of the caller - but it all boils down to: if you hand out your code a skilled person can do to it whatever he wants... ... Developing More Secure Microsoft ASP.NET 2.0 Applications ... assemblies are distributed to end user systems (they are not installed ... aspect as developers/end users reusing my .NET assemblies in their own ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Best Practise: Many Small or viewer Large assemblies
    ... (In my opinion anyway) ... The thing is that the assemblies are often very small. ... Personally I like the first option, since I don't have to load this monster ... with hundreds of projects in a single solution, ...
    (microsoft.public.dotnet.general)
  • Re: How to setup .....
    ... Below is the step-by-step process of setting up VB.NET using Installshield ... .NET Assemblies can be installed local to the application or to ... the Global Assembly Cache. ...
    (microsoft.public.dotnet.languages.vb.controls)
  • Re: Using .NET Assembly as stored proc
    ... The assembly code will execute using the current connection and security context if you specify a connection string of "context connection=true". ... be aware that normal ownership chaining rules don't apply because SQL executed within CLR assemblies is considered dynamic and breaks the ownership chain. ... regarding using .NET Assemblies as stored procs (or referencing them ... proc to be return to the client calling the stored proc as a SQL ...
    (microsoft.public.sqlserver.programming)