Re: Security of C# dll
- From: "Homer Simpson" <homer@moe's.com>
- Date: Wed, 6 Jul 2005 15:07:49 -0500
My original concern was just preventing my dlls from being decompiled... or
at least making the process as difficult as possible. I was just looking at
the Dotfuscator website and learning a little more about this. I'm looking
to protect my intellectual property and methodologies more than preventing
someone from maliciously using my code.
Thanks,
Scott
"Peter Rilling" <peter@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23IHAHvlgFHA.2896@xxxxxxxxxxxxxxxxxxxxxxx
> Define what you mean by "secure".
>
> There is secure in that no one can hack the code and cause malicious
> things
> to happen, or secure in that your code cannot be decompiled, or secure in
> that no one can inherit from your libraries (which can also be used for
> malicious purposes), or secure in that different trust levels are assigned
> based on where the code was invoked from.
>
>
> "Homer Simpson" <homer@moe's.com> wrote in message
> news:eaWD0ilgFHA.2156@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi Everyone,
>>
>> How secure are C# DLLs? I knowVBA can easily be opened with a variety of
>> tools found on the internet but how about C#? How can I make my DLLs more
>> secure?
>>
>> Thanks,
>> Scott
>>
>>
>
>
.
- Follow-Ups:
- Re: Security of C# dll
- From: Cool Guy
- Re: Security of C# dll
- References:
- Security of C# dll
- From: Homer Simpson
- Re: Security of C# dll
- From: Peter Rilling
- Security of C# dll
- Prev by Date: Re: Master/Detail question
- Next by Date: Re: XML Serializer
- Previous by thread: Re: Security of C# dll
- Next by thread: Re: Security of C# dll
- Index(es):
Relevant Pages
|