🚀 go-pugleaf

Hi mike,

Some protection is better than no protection. I
believe you must keep in mind the possible limitations
of the solution you choose.

I can't think of a way of creating a system unique
identifier without including hardware info.
As such, what will happen if the user has to change
something in his machine (a network adapter card,
flash a BIOS update, replace the hard disk, etc.)?
The system identifier will change and the user will
need a new key, which you shouldn't refuse to provide.

How will you be able to detect if the user simply
installed your app in a new machine and is lying
to you just to get a new key? (Get 2 or 3 for the
price of 1)
Have you thought about that?

Eudy

Mike H. wrote:
> Hello,
> 
> to protect my application from distribution, i like to generare a unique
> identifier of the computer where my application runs. the user give us his
> unique id und he gets a key from us. his puts the key inside the
> application, which write the key to the registry.
> 
> Everytime when the application starts its compare the unique identifier with
> the key.
> 
> My question is how to create a unique identifier of a computer. important
> is, that this identifier is different from others computer.
> 
> perhabs, the identifier could include hardeware information.
> 
> any ideas? perhabs anybody has already solve my problem.
> 
> mike
> 
>