Re: Securing Software with License
- From: grant@xxxxxxxxxxxxxxx
- Date: 26 Jan 2006 15:28:09 -0800
I agree with pretty much everything John said above. There are really
two aspects to consider. The first is generating customer unique
license keys that can't be reverse engineered by inspecting your code.
For this you really need a system that uses some form of public key
encryption. Our company, Infralution, offers a low cost licensing
solution that does this (www.infralution.com/licensing.html).
The second aspect is preventing crackers simply bypassing your license
checks by nulling out statements or simply recompiling your whole
application. Unfortunately there is bullet proof way to do this. If
you visit some of the crack sites you will see that just about all of
the protection/obfuscation products have themselves been cracked - so
your best insurance is the sort of approach that John recommended where
at least the cracker will have to put some effort in understanding your
particular code.
There is also really good article on Code Project
(http://www.codeproject.com/gen/design/UnconventialWisdom.asp) about
the balance between protecting your code and making life difficult for
your legitimate customers.
Grant Frisken
Infralution
www.infralution.com
.
- References:
- Re: Securing Software with License
- From: Frans Bouma [C# MVP]
- Re: Securing Software with License
- From: john smith
- Re: Securing Software with License
- Prev by Date: Re: Dynamic array in VB NET
- Next by Date: Re: Importing a Com Object
- Previous by thread: Re: Securing Software with License
- Next by thread: Re: Securing Software with License
- Index(es):
Relevant Pages
|
Loading