Re: Copy protection for a .NET application
From: William Stacey [MVP] (staceywREMOVE_at_mvps.org)
Date: 11/29/04
- Next message: Klaus H. Probst: "Re: .NET on Win98"
- Previous message: Jacky Luk: ".NET on Win98"
- In reply to: Salih Goncu: "RE: Copy protection for a .NET application"
- Next in thread: Massimo: "Re: Copy protection for a .NET application"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Nov 2004 01:34:28 -0500
True. But it is no harder to branch around this then anything else if your
talking patching (not simple keygens). If keeping secrets, then maybe a
good way to go but seems to have all the draw backs of a dongle which I
would never buy (again).
-- William Stacey, MVP http://mvp.support.microsoft.com "Salih Goncu" <Salih Goncu@discussions.microsoft.com> wrote in message news:1151F786-8CB6-4261-89FB-4D320232D152@microsoft.com... > Hi, all. > > Well, reading all the thread, there's a really good way to make a copy > protection for a IL (or bytecode for Java) available. Besides obfuscation, > which is good for many of the cases, the approach I'll tell you is for *real* > paranoids. > > In protecting some piece of code from analysis requires that it is > impossible to reach that piece of code from within the context of > application, that is, run that code somewhere else. > > The best candidate, as far as I know, is smartcards with crypto > co-processors. > > Have the smartcard generate a key pair for you and store the private key > inside itself, never telling it even you. Then, put a piece of code in the > smartcard and give it the access credidentals with only the public key that > the card delivered you. Use a secure communication protocol between the > smartcard and the computer, so that nobody will be able to intercept the data > transmitted. > > When your program is running as shareware, it won't require the vital piece > of code that needs to execute in the smartcard. But when it is licensed, you > give your customer the card and the corresponding public key. So, when in > licensed mode, the card executes the vital code, and returns only the > required results meaningful only for that license or context. (The code > inside the smartcard may be dependent on some data or other code in your > application, but your application *must* be dependent on this code piece.) > > I used this approach on some projects, and proved well. You can check out > possible cards supported by Windows CSP from Gemplus, Sclumberger and Orga. > The capacity of cards range from 8 to 128 Kbytes, which is sufficient for > many types of applications. > > As this is the hardest nut to crack, this is also very hard to code, so you > decide if you want it or not... > > Salih > > "Massimo" wrote: > > > I'm planning to develop a .NET application using C#, in order to sell it as > > a shareware and/or as a full package, so I'll need a good way to protect it > > against piracy. I know some ways to protect it (activation, serial keys, > > etc.), but my concern is: how can any copy protection mechanism work when > > you can always disassemble it and read the source code? Even if I use a > > native C++ DLL for my copy protection, the point where it's called from the > > C# code can always be found. > > Any good tips about this? > > > > Thanks > > > > > > Massimo > > > >
- Next message: Klaus H. Probst: "Re: .NET on Win98"
- Previous message: Jacky Luk: ".NET on Win98"
- In reply to: Salih Goncu: "RE: Copy protection for a .NET application"
- Next in thread: Massimo: "Re: Copy protection for a .NET application"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
