temp data and storage.

Veerugadde
11th May 2007 18:28 UTC

temp data and storage.
Hello all,

I am trying to develop an installer which should be set to disable state after installation is successful. If i make count of the installer runs by initializing with zero and increase the count upon .onInstSuccess function.When the user tries to run installer next time, installer aborts.As sometimes users who downloaded the installer file may pass on to illegal users which we want to prevent.

I am stuck with the count value storage: as can i store the count value on the stack or temporary folder? If the temporary folder is stored on user machine it will be useless.Is there any way to handle the storage of data.

Could anyone please suggest me whether the above idea is sufficient enough to prevent the illegal use or pass on any new suggestions?

Thanks...

demiller9
11th May 2007 19:48 UTC

It sounds like you want to store the count in the executable itself. But this would also be easy to bypass, because someone could download the file and then make a copy before they execute it the first time.

The protection you are trying to create is dificult to do, especially if you want to prevent a semi-knowledgeable user from defeating it. I think the best method is to have a registration key generated by your website and dependent upon some machine or user specific data.

Sheik
11th May 2007 20:44 UTC

I have to be honest, I don't think what you want to do
will be possible...

At least, not without being defeated easily.

1) I would just make a copy of the original file first.

2) I would make the Installer's .exe unwritable,
(say by burning it off to a CD first).
Then I would run the Installer from that image.
You aren't going to be able to mod the Installer image on the CDROM, so my image would remain pristine and useable over and over.

I don't think you will find an easy solution to your problem.

Scott

Veerugadde
11th May 2007 22:27 UTC

Originally posted by demiller9
It sounds like you want to store the count in the executable itself. But this would also be easy to bypass, because someone could download the file and then make a copy before they execute it the first time.

The protection you are trying to create is dificult to do, especially if you want to prevent a semi-knowledgeable user from defeating it. I think the best method is to have a registration key generated by your website and dependent upon some machine or user specific data.

Thanks alot for sharing your thoughts. If we generate the registration key for installer , is there any possibility that i can make the key useful for onetime installation process. I will go in depth to explain the issue as if we want the user to have the key which should be useful for onetime and should not allow the other user if he uses the same key with a copied installer.

I really need your suggestions...

Thanks.

Red Wine
12th May 2007 08:19 UTC

I really need your suggestions...

Thanks.

Implement the desired security in application side rather than installer side.
Go find on market a scheme that suits your requirements or build your own to secure your software.
An activation method like those used by microsoft (WGA-OGA) or Adobe or Symantec etc would be great idea.
If you insist to implement a method in installer side, here is a good one,

http://forums.winamp.com/showthread.php?threadid=261704