Re: Breaking .NET Compact Framework code - how easy is it

Tech-Archive recommends: Fix windows errors by optimizing your registry

Simon,

Here's Reflector: http://www.aisto.com/roeder/dotnet/

--
Ginny Caughey
..NET Compact Framework MVP


"Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
news:eS4SsOIDGHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
>I have been thinking about this further. I know strong naming assemblies
>should prevent a "hacked" version from running - strong nameing assemblies
>should be common practice anyway. But lets say you are using a tool such as
>Reflector (where can I get Reflector btw? - to test my own code) you are
>able to decompile the assembly to source code successfully. In this case it
>doesn't matter where you put the algorithm - whether its managed/unmanged
>or embedded as a resource etc. All the cracker has to do is alter the
>condition on return from the algorithm call to always pass regardless of
>the result.
>
> So it seems the most effective way to stop pirate copies of your software
> is to ensure it cannot be decompiled.
>
> Cheers
> Simon.
>
> "n33470" <n33470@xxxxxxxxxxx> wrote in message
> news:1135862616.470831.246100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> At the risk of sounding naive, is this even a valid concern? If the
>> assemblies have been strong named, should that alone prevent the issue
>> of running a "tampered" assembly? I thought that was the whole point
>> of strong naming....to prevent running "hacked" assemblies.
>>
>> As far as running ILDASM to look at source code, yes you can do that.
>> If viewing source code is a concern of yours, then use an obfuscator to
>> scramble the code before you release the app to production. The
>> downside of obfuscation, is that you cannot log a "readable" stack
>> trace in any error logs that you create.
>>
>> Curious what your thoughts are on the strong naming issue.
>>
>> --steve
>>
>
>


.

Relevant Pages

  • Re: Breaking .NET Compact Framework code - how easy is it
    ... that Reflector is quite amazing and worring!! ... encryption algorithm to generate licence numbers. ... I know strong naming assemblies ... >>> As far as running ILDASM to look at source code, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Breaking .NET Compact Framework code - how easy is it
    ... I know strong naming assemblies ... > As far as running ILDASM to look at source code, ... > trace in any error logs that you create. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Given a C#.NET assembly, what information can you get?
    ... resources and even create a project file with assembly ... How can I reverse it back to source code with Reflector? ... of .NET assemblies see: http://www.dimecasts.net/Casts/CastDetails/28 ...
    (microsoft.public.dotnet.general)
  • Re: IComparer and Sort
    ... Now I get the same contents as you have in QuickSort. ... Earlier I used this location in reflector ... That _could_ happen if you have multiple versions of the .NET assemblies ... not in the GAC, then that's probably your problem right there. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: IComparer and Sort
    ... Now I get the same contents as you have in QuickSort. ... Earlier I used this location in reflector ... That _could_ happen if you have multiple versions of the .NET assemblies ... not in the GAC, then that's probably your problem right there. ...
    (microsoft.public.dotnet.languages.csharp)