Re: Copy protection for a .NET application

From: C-Services Holland b.v. (csh_at_REMOVEcsh4u.nl)
Date: 12/02/04 

Date: Thu, 02 Dec 2004 16:53:35 +0100

William Stacey [MVP] wrote:
>>The problem with decrypting the code yourself is that you have a readily
>>accessable decryption module in your software to decrypt the DLL. That
>>would make it a breeze for any decent cracker to break your protection.
>
>
> True. But you have equal access to the either code in memory using a
> debugger. So it does raise the bar, but not too high for crackers. They
> use debugger anyway (after ildasm fails), so it is not much difference for
> them.
>

Not really. The decrypting part is in the hardlock, unaccessable by
debuggers :) From the tech docs I've read, they also employ
anti-debugging techniques to prevent on the fly inspection of things
going on.

But as I said. Nothing is impossible to crack, it's just how much time
and effort is one willing to spend. 

-- 
Rinze van Huizen
C-Services Holland b.v.

Relevant Pages

  • Re: encrypted source file support in jdk?
    ... eyes who have obtained the class files and using the debugger to get ... If you are looking to protect your code from the owner/user of the ... of decrypting your ciphertext /and/ all instances of decrypted ... yours as a "remote dongle" where everything is actually run. ...
    (comp.lang.java.help)
  • Re: Copy protection for a .NET application
    ... > The problem with decrypting the code yourself is that you have a readily ... > would make it a breeze for any decent cracker to break your protection. ... use debugger anyway, so it is not much difference for ... But I do know the hardlock encryption is very ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Copy protection for a .NET application
    ... > The problem with decrypting the code yourself is that you have a readily ... > would make it a breeze for any decent cracker to break your protection. ... use debugger anyway, so it is not much difference for ... But I do know the hardlock encryption is very ...
    (microsoft.public.dotnet.framework)
  • Re: Copy protection for a .NET application
    ... > The problem with decrypting the code yourself is that you have a readily ... > would make it a breeze for any decent cracker to break your protection. ... use debugger anyway, so it is not much difference for ... But I do know the hardlock encryption is very ...
    (microsoft.public.dotnet.general)
  • Re: Copy protection for a .NET application
    ... >>accessable decryption module in your software to decrypt the DLL. ... >>would make it a breeze for any decent cracker to break your protection. ... > use debugger anyway, so it is not much difference for ... The decrypting part is in the hardlock, ...
    (microsoft.public.dotnet.framework)