On 31/08/12 21:18, Mark Morgan Lloyd wrote:
Of course, an even safer way would be to leave the executable alone and to put an early check in the startup code that a subsidiary key file existed, and for that key to include something that identified the machine or site on which the program was entitled to run.
Take a look at OnGaurd. It has many ways of doing this. We use it in our commercial software (linux and windows) to lease our software on a yearly basis, or to enabled a 1 month trial etc. You can even lock your application down to a specific PC.
https://github.com/graemeg/onguard Graeme. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
