On Sep 23, 2:32 am, kanis <[EMAIL PROTECTED]> wrote: > It's a sound idea, but I'm not sure it's right for my application. If > I use a message based off some system parameters the user can't easily > modify, they're going to need to contact me to get a new key (I'd call > it an activation key at that point) whenever they upgrade to a new > system, change the operating system version, or change whatever > underlying parameters control this message. I don't want to put users > through that or even spend the time to deal with it myself. > > Unless that's still not what you meant?
There are variations on this - e.g. generate a random number when you run the program for the first time on a system. Which has similar problems. But if you then also linked their product key to their e- mail account, you can set up a website for them to retrieve new activation keys without having to bother you on the phone/email - and also detect abuse of the system, if some email address gets used for generating a lot of keys. I wonder if anybody has patented this... I only have ordinary skill in the art. (Pesky overly general software patents...) :p --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
