Chrysalid
Newbie
- Joined
- Jun 13, 2004
- Messages
- 160
- Reaction score
- 0
This might sound stupid at first, but I hope you get my point.
I've been looking on several methods of how to implement an effective and half-standalone ( requires Internet usage on first time but not after that ) copy protection. My idea is as follows.
As some of you may know, modern hard drive serial numbers are very unique. They are also, to my knowledge, so hardcoded into the firmware that they cannot be changed without screwing up the drive's control software. My idea would be that the user wanting to buy my product is first required to download an executable ( shipped with usage agreement, stating that the tool sends required authentication information to me, the user has to accept that or not to use my software ). This program would extract the user's hard drives' serial numbers, then email them to me for processing. Then, I could build a special version for each registered user. My product's code would then include the crypted serial number, which it would decrypt during installation and execution, comparing the hardcoded serial into the one with the user's hdd.
What do you think? Is this sensible at all or worth trying?
I've been looking on several methods of how to implement an effective and half-standalone ( requires Internet usage on first time but not after that ) copy protection. My idea is as follows.
As some of you may know, modern hard drive serial numbers are very unique. They are also, to my knowledge, so hardcoded into the firmware that they cannot be changed without screwing up the drive's control software. My idea would be that the user wanting to buy my product is first required to download an executable ( shipped with usage agreement, stating that the tool sends required authentication information to me, the user has to accept that or not to use my software ). This program would extract the user's hard drives' serial numbers, then email them to me for processing. Then, I could build a special version for each registered user. My product's code would then include the crypted serial number, which it would decrypt during installation and execution, comparing the hardcoded serial into the one with the user's hdd.
What do you think? Is this sensible at all or worth trying?