Source Code

[elzij]

The source code is given to ther user.
Is there anyway that i can define the expiry date in it? Say i give the source code today. It should run fine for a month and after a month the user should not have the required access to the software. This is usually not possible when the source code is given to the user, in case somebody has come across a similar situation please advice me on the same.

 

[WMK]

There is certinly no "fool proof" (or hacker-proof) way that I can think of.

HOWEVER, you might be able to figure out something with an "encrypted" VALUE clause based on the date and do some arithmetic on it - causing (at least) a run-time error when I certain amount of time has passed.

***

This sounds like what "contracts" (EULA) are for.

Bill Klein

 

[Crox]

Why did the user get the source? But even when you give the source, it is possible to change the meaningful names into things like aa, ab, ac, ad, etc. So no one has easy access to the source so they will probably never change it anyway.

You can encrypt any readable working-storage info and decrypt it at runtime. That will make also such a program unmaintainable... but the source is there....

The program can also have other kinds of limits like file-size, table-size, etc. so after some time, it will need some maintenance.

But... why do you give the source if you don't want to give it. Isn't it possible to give a working module with your own time-limits inside and if they want to see the source, youi show them once, on your notebook and after the inspection, you take it with you....???

Years ago, some companies like az-tech had encryption systems which makes it possible to use some product for a limited time.