Copy protection ideas

  • Thread starter Thread starter David
  • Start date Start date
D

David

I would like to set up a copy protection scheme where the application must
be provided
with an unlock code before it can be installed.

Any ideas for a relatively simply system for doing this ? I seem to remember
something like reading PC BIOS, adding the current date and XORING with a
fudge factor to create a code that the user rings up and quotes. In return
we give then an unlock code.

(I have also forgotten how to read BIOS).

Thanks for any help

Regards

David
 
David said:
I would like to set up a copy protection scheme where the application must
be provided
with an unlock code before it can be installed.

Licensing support in the .NET Framework:

..NET Framework Developer's Guide -- Licensing Components and Controls
<URL:http://msdn.microsoft.com/library/en-us/cpguide/html/cpconlicensingcomponentscontrols.asp>

..NET Licensing
<URL:http://windowsforms.net/articles/Licensing.aspx>

Free components:

Aspose.License
<URL:http://www.aspose.com/Products/Aspose.License/>

Commercial components:

XHEO|Licensing
<URL:http://www.xheo.com/products/enterprise/licensing/>

Infralution Licensing System
<URL:http://www.infralution.com/licensing.html>
 
I can see how this licenses a control. Can you explain how these are used to
protect the application istelf ? I am not sure how I generate the serial
number for each copy of the software I distribute.

Thanks
 
I am looking for a "simple" technique.

The users of my particular application will not go to the extend of
decompiling the application.

They are more likely to make unauthorised copies of the software to run on
more than one machine.

Each time they install our software at a site, I want the install program to
display a code that is unique to that machine in some way.
The customer then contacts us and we give them a key to type in that allows
the application to be installed and run.

If I knew some useful data locations on the PC or in the registry that I can
read and use to create this lock code then I could sum the value of these
parameters, add the date and xor to provide a code.

Thanks
 
Contelmo,
whichever technique is ineffective if the program can be decompiled !
True. However not any method is be100% proof.

There is forever logic involved.

In a normal situation there are not so much users who know how to decompile,
to change it, to compile and than to use it.

This is in most countries protected by law when it is about illegal use of
the software.

With what I don't say "don't protect it", that is everybodies own decission.

Cor
 
whichever technique is ineffective if the program can be decompiled !
True. However not any method is be100% proof.

There is forever logic involved.

In a normal situation there are not so much users who know how to
decompile, to change it, to compile and than to use it.

This is in most countries protected by law when it is about illegal use of
the software.

With what I don't say "don't protect it", that is everybodies own
decission.

Hi Cor,
they are pushing to the patent!

you must patent the software e/o algorithm in *all* the nations (cost
exaggerated for a single developer!). but he remembers, than your code, he
never must not have been used before from nobody.

not there is no association that you protection. you must verify that the
code was yours...decompiling (illegal use) the program !!! and if also a
portion of code is various you must pay the moral damages !

Marcello
 
The .NET Framework licensing is very easy to pirate. Just look for the lic
extension & then open it with a text editor.

As for decompilers: There are some fantastic ones out there for VB.NET &
they do do a good job. I have used them to test my own compiled source code,
and was shocked at the results.

There are a few programs that stop your program from being decompiled. One
of which is on the 'got dot net' user sample page
(http://www.gotdotnet.com/community/usersamples/). The good thing about it is
its free & it works extremely efficiently.
 
The .NET Framework licensing is very easy to pirate. Just look for the lic
extension & then open it with a text editor.

As for decompilers: There are some fantastic ones out there for VB.NET &
they do do a good job. I have used them to test my own compiled source
code,
and was shocked at the results.

There are a few programs that stop your program from being decompiled. One
of which is on the 'got dot net' user sample page
(http://www.gotdotnet.com/community/usersamples/). The good thing about it
is
its free & it works extremely efficiently.

other obfuscator *only* renaming & overloads method!

try to decompiled with all your decompilers :-o this simple application
protect with my pre-release obfuscator:
http://xoomer.virgilio.it/cantelmosoftware/net/TryMe.zip

Marcello
 
IMO This is the most miserable and useless example of licensing ever. The
code only explains the mechanism of the license and provides absolutely no
assistance whatsoever in creating a secure component. What can be dumber
than loading a file that says "This is a licensed component"?

--
Bob Powell [MVP]
Visual C#, System.Drawing

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
 
Back
Top