Re: Strong Names Secure???

From: Nicole Calinoiu (calinoiu)
Date: 09/16/05 

Date: Fri, 16 Sep 2005 08:14:24 -0400

Like Dominick mentioned, your assembly will be subject to potential
decompilation once it's out of your hands. The most common means of
attempting to minimize the impact of such decompilation is obfuscation,
where the underlying approach is to make the decompiled code sufficiently
difficult to understand that it's not worth the "reader's" time.

"VISHAL" <VISHAL@discussions.microsoft.com> wrote in message
news:2DAD7562-8885-445F-81F5-B0ED6E94340F@microsoft.com...
>I would like to secure my assemblies.I would not like the users going in
>and
> making changes in my assemblies.Once released i would like that my
> assemblies
> be tamper proof.
>
> Thanks,
> Vishal
>
> "Nicole Calinoiu" wrote:
>
>> "VISHAL" <VISHAL@discussions.microsoft.com> wrote in message
>> news:D864B187-6231-4B01-9AF8-81E3608217EA@microsoft.com...
>> > According to this article it is very easy to break strong names
>> >
>> > http://www.codeproject.com/dotnet/NeCoder03.asp
>>
>> Removal of a strong name from an assembly does not constitute "breaking"
>> of
>> the strong name mechanism.
>>
>>
>> > Is there a way other than strong names to secure .Net assemblies
>>
>> Exactly what kind of "securing" are you interested in applying? Against
>> what threat(s) are you attempting to protect the users of your
>> assemblies?
>>
>>
>>

Relevant Pages

  • ANN: 9Rays.Spices.Net v3.3 has been published
    ... Spices.UML plugin. ... * Own assembly verifier replaces old verifier. ... * Added new command for assemblies verification - Verify all assemblies ... * Prevention from Spices.Decompiler decompilation: ...
    (microsoft.public.dotnet.languages.csharp)
  • ANN: 9Rays.Spices.Net v3.3 has been published
    ... Spices.UML plugin. ... * Own assembly verifier replaces old verifier. ... * Added new command for assemblies verification - Verify all assemblies ... * Prevention from Spices.Decompiler decompilation: ...
    (microsoft.public.dotnet.languages.vb)
  • ANN: 9Rays.Spices.Net v3.3 has been published
    ... Spices.UML plugin. ... * Own assembly verifier replaces old verifier. ... * Added new command for assemblies verification - Verify all assemblies ... * Prevention from Spices.Decompiler decompilation: ...
    (microsoft.public.dotnet.framework.compactframework)
  • ANN: 9Rays.Spices.Net (.Net explorer, decompiler, obfuscator) v3.3 has been published
    ... Spices.UML plugin. ... * Own assembly verifier replaces old verifier. ... * Added new command for assemblies verification - Verify all assemblies ... * Prevention from Spices.Decompiler decompilation: ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Deployment frustrations
    ... If there are links with assemblies via maps in ports I use WMI to delete ... --receieve location which uses the pipeline from the common ... the IDE squaks about a reference to PartyX ...
    (microsoft.public.biztalk.general)