The scheme I've settled on is ... for the key, I only require installations to have unique keys. I have a list of keys stored in a table from which they are dispensed. The software is intelligent enough to know the difference between a real and fake key.
It is possible for this scheme to be broken, but the focus of my attention isn't on people breaking the installation key, it's on protecting access to maintenance releases. The reasoning is twofold: (1) maintenance introduces ongoing enhancements and new features, presumably attractive enough to be worth the price, and (2) the code isn't so perfect that it will run forever without attention. Odds are "good enough" that a business which depends on the software will want or need maintenance at some point. When an installation attempts to download maintenance using a feature for this purpose, it first sends the key to the server, which returns either a valid URL for the maintenance, or something else. Bill _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
