🚀 go-pugleaf

What i have been doing is:

- The user enters their code into the app.  The app connects to a script on 
my server that verifies the code is valid (you can do this with the indy or 
fastnet http component).  I use php and mysql for my server-side script.
- The script on my server keeps track of the date the code was entered, and 
does not allow the code to be entered for at least 60 days beyond that date 
(this seems to prevent friend code sharing)
- The code is stored in the windows registry in 2 locations.  The first 
location is to store the code as a string, the second stores the code as an 
encrypted binary value (you'll need to find a simple encryption algorithm to 
convert your code).  When your app runs, get both codes from the registry, 
decrypt the second code, and make sure they match.

Hope this can help you or point you in the right direction...

~Kelly



"Per Elms�ter" <perelms@hotmail.com> wrote in message 
news:43a17420$3@newsgroups.borland.com...
> I'll be ready to start distributing the app I've been working on in a 
> couple
> of weeks. Time to look into a strategy for licensing and allowing the
> customers to download a trial version. I've been Googling the groups quite
> intensively now but I didn't come up
> with anything interesting for me. Most third party tools I found were 
> rather
> expensive and really sophisticated. I'm not real worried the professional
> crackers will spend any time with my app. All I want is to keep normal
> people honest
>
> 1. They download a time limited trial version.
> 2. They like it and register for a license key as the pay for the 
> product.In
> the $50 range
>
> Point number two is the important part. Once they've downloaded and
> evaluated my app, I want them to come back and pay for it. Some kind of
> registration procedure that will let them continue to run the app on the
> computer it's already downloaded to, but keep them from giving away the
> license key to their friends at least. Ie the key wont be any good on
> another machine.
>
> How do you solve these matters?
> Can somebody recommend either a priceworthy third-party tool, where I 
> don't
> have to pay a bundle for making my source code cracksafe.
> Or can you recommend a strategy that I could employ myself.
> I'm distributing the product as a Windows Installer package.
>
> -- 
> Perre
>
> Symfoni, en kost- och tr�ningsdagbok
> http://www.kostforum.se
>
>
> 

Thanks Kelly

I have mySql and php available. I'll look into that and the http components
you suggest.


Kelly Domalik wrote:
> What i have been doing is:
>
> - The user enters their code into the app.  The app connects to a
> script on my server that verifies the code is valid (you can do this
> with the indy or fastnet http component).  I use php and mysql for my
> server-side script. - The script on my server keeps track of the date
> the code was entered, and does not allow the code to be entered for
> at least 60 days beyond that date (this seems to prevent friend code
> sharing) - The code is stored in the windows registry in 2 locations.
> The first location is to store the code as a string, the second
> stores the code as an encrypted binary value (you'll need to find a
> simple encryption algorithm to convert your code).  When your app
> runs, get both codes from the registry, decrypt the second code, and
> make sure they match.
>
> Hope this can help you or point you in the right direction...
>
> ~Kelly
>
>
>
> "Per Elms�ter" <perelms@hotmail.com> wrote in message
> news:43a17420$3@newsgroups.borland.com...
>> I'll be ready to start distributing the app I've been working on in a
>> couple
>> of weeks. Time to look into a strategy for licensing and allowing the
>> customers to download a trial version. I've been Googling the groups
>> quite intensively now but I didn't come up
>> with anything interesting for me. Most third party tools I found were
>> rather
>> expensive and really sophisticated. I'm not real worried the
>> professional crackers will spend any time with my app. All I want is
>> to keep normal people honest
>>
>> 1. They download a time limited trial version.
>> 2. They like it and register for a license key as the pay for the
>> product.In
>> the $50 range
>>
>> Point number two is the important part. Once they've downloaded and
>> evaluated my app, I want them to come back and pay for it. Some kind
>> of registration procedure that will let them continue to run the app
>> on the computer it's already downloaded to, but keep them from
>> giving away the license key to their friends at least. Ie the key
>> wont be any good on another machine.
>>
>> How do you solve these matters?
>> Can somebody recommend either a priceworthy third-party tool, where I
>> don't
>> have to pay a bundle for making my source code cracksafe.
>> Or can you recommend a strategy that I could employ myself.
>> I'm distributing the product as a Windows Installer package.
>>
>> --
>> Perre
>>
>> Symfoni, en kost- och tr�ningsdagbok
>> http://www.kostforum.se

-- 
Perre

Symfoni, en kost- och tr�ningsdagbok
http://www.kostforum.se