Printable View
I know this is not a direct function of SB, but I am looking for information on ways to construct a key to tie a program to a particular computer and after having built a license file for that computer, where to put it.
Should the license file go into the same folder as the EXE as it will be read only (until it expires and gets replaced).
Thanks, Bob Roos
Bob,
First of all, license protection should be handled at application level and not installation level.
But to answer your question, from the technical point of view it's not possible to retrieve such information (especially not in the days of virtual machines). You can try to get your hands on the CPU serial number (if the CPU supports it and the feature is enabled), the NIC address(es), built-in HD serial number (if available; but NOT the volume serial number!), etc. Please note that all this is not bulletproof at all! Most of this will not work as expected in virtual machines (and quite a few users are running virtual machines today). For example, in our office all work is done in virtual machines. You can simply copy one VM over to another machine(s) and use it there.
BTW, don't waste your time with this kind of license protection. Hackers will crack it within minutes. There are so powerful disassembler tools available today that it does not make sense to develop your "own" protection mechanism. It's impossible to construct a key to tie a program to a particular computer.
Friedrich
Friedrich, Thank you for your response. Yes, I was thinking at the application level. You were the best source of information in this area that I knew.Quote:
Originally Posted by linder
What would you recommend for program protection then?
Thanks, Bob
Bob,
IMO, Armadillo is the best license protection system available -BUT- there is always a "but" in this imperfect world <g>. There is a "SoftwarePassport - Is this still available?" thread in the SoftVelocity third-party NG. As I understand it, there are some problems with the product at the moment.
And always keep in mind that the hacker groups can crack any software. The harder you think the protection is to "hack" the sooner you'll find yourself on all the well known crack sites. There are so powerful tools available today to disassemble any (even protected) apps. The tools disassemble your apps, convert the assembly code into C code and they can see what you are doing to protect your apps. Even the keygens are generated automatically today. Or patches to work around your protection.
Friedrich
As it has been said, "Locks are to keep honest people honest".
I am not sure if my product will be worth the hacking effort.
Thanks, Bob