in reply to License key for script

Depending on exactly what you're asking about something may be possible. What I think you're asking, though, is not likely to do you much good. Please clarify what it is you want.

Are you wanting to write a program in Perl, distribute the source code to the operators of some web server you don't control, and have it not run once a certain date is past?

Are you wanting to have a CGI program on your own server you can have stop returning results after a certain amount of time or a certain number of total results?

Do you want to have users sign up for a web application with a username and password (or some other authentication) and stop authenticating them after some point in time?

Are you wanting to wrap your Perl program with a compiled binary program that checks some license status then decrypts your program and hands it to the interpreter?

Any of these has a different answer and different points to discuss from the others. I'm not really sure which it is you're asking, or if you're asking something else entirely.

Replies are listed 'Best First'.
Re^2: License key for script
by shanu_040 (Sexton) on Sep 07, 2010 at 05:11 UTC

    I should explain it more clearly, Thanks you have done it form me.

    I am looking for...

    Are you wanting to write a program in Perl, distribute the source code to the operators of some web server you don't control, and have it not run once a certain date is past?

    please help me

      It is unfortunate that is what you need to do, because there really is no satisfactory way to give others access to their own copy of your program and enforce a license restriction on it. This is especially true when you provide the source to them.

      There are some possible workarounds. None of them are pleasant. What's worse is that the workarounds for making your Perl code more secure on a server you don't control still don't make rejecting a license or ending a subscription foolproof as a technical measure. Even a compiled program that decrypts most of itself at run time can be broken by a motivated person with knowledge of readily available tools.

      The only reliable way to enforce subscriptions is to control where the code runs. You can do that by running it on your own server and selling access to it or by enforcing the subscription in a reliable and responsive court system. The latter is often more trouble than it is worth.

        Very much agree on it. What I have in my mind is when client sends a request(1st request) for a resource. Server(Requested Server) will check for its subscription on my server and do a database transaction(or set some cookies on client)on requested server.If subscription is over than it may redirect to some other location and is not than it will display the resource.

        What do you suggest.

          A reply falls below the community's threshold of quality. You may see it by logging in.