Making your own license?

[eskimoavenue]

Hi,

I have the unlimited runtime as part of the full a5 package and I am thinking of getting some subcontractors the right to use my app as long as they work for me. However, I don't want them to distribute the app or use it anymore if they stop being my subcontractor. In other words, I would like to make my own license key that changes every month or so, maybe some mathematical version of year/date or so that is very hard to figure out.

I am not asking for a full step by step guide, but do you think it can be done and in what way would you do it?

Thanks!
R

[RevMK]

Re: Making your own license?

Hi R,

You can set a throttle on the number of people that can use the runtime.

As far as checking the user - you could have a login system that connects to a web server you own to validate that the user can enter the application.

For example: the server would hold a copy of the 'licence key' and 'access flag'. You could then carry out a check every month/week/etc to check the current status. If you forced this step to happen every so often it would give a reasonable level of control.

If you encrypted the tables you would also help prevent side access.

Disadvantages:
1) It requires internet access at least once a month
2) It is not 100% fool proof - think users never logging out.

Hope this gives some idea.

[Ted Giles]

Re: Making your own license?

If the subbies are accessing from a network server, then I suggest that you use the Alpha Security.

If you are deploying the apps for use on a single PC, suggest that you have a daily/weekly/monthly e-mail which sends a script to the PC and allows authorisation.

This will require that the Alpha e-mail client is used and an automated script to pick up the mail and process it, or you could embed say 12 pass keys and send each one out on a regular basis. Say monthly. No key - no app. You may need to put a caveat into the agreement with your subbies that the software will stop working without the appropriate key or they may sue.

The problem is not starting the app, it's stopping abuse.

Let us know what you do please as there is likely to be some interest.

[CALocklin]

Re: Making your own license?

Yes, it can be done. It took me many, many, many, many, many hours (i.e., not cheap) to figure out a process for creating a registration routine that would protect from hacking and copying. The registration number itself includes a link to the computer, a link to the application name, an optional limit on the number of users, and an optional expiration date.

However, that's only half the problem. In addition to the registration number itself, there are a few other things that need to be done to make it very difficult for someone to hack the program and bypass the registration. (Nothing is perfect when it comes to keeping hackers out but mine is complex enough that when some problems occurred during early tests it once took me over 2 hours to figure out how to get things back to a clean state so I could start over again.)

Don't ask me how I did it because I couldn't tell you even if I wanted to. The code is complex enough and enough years have gone by that I don't remember what I did. The only way I can decode the registration number is to go through the code step by step.

You may be able to do something simpler that you feel is sufficient to meet your needs.

You can find out more about my AIMS Registration routines along with my other addins on this page. (It still says "New" but it's not really that new anymore. The first one was sold in early 2006. I suppose I should update the page but I've been more concerned with other things lately.)

[porjoe]

Re: Making your own license?

oops