doing trial periods

Monte Goulding monte at sweattechnologies.com
Sun Apr 25 23:56:08 EDT 2004


 There are more issues with this
>method:
> - if you were changing the standalone then you would need to have a second
>standalone to do it
> - any hacker worth his salt would notice the change in the modification
>date of the standalone and find the string and change it to 2020
> - for this to work the file needs to be unpassword protected so
>anyone with
>rev can break it in about 2 mins

OOPS... I forgot one:
rev date and time commands just return the same value that user can modify
in the operating system. So you can just wind your machine back to get past
this.

One way to get past this is instead of calculating and saving an expiry date
you can do the following:
 - save a custom property set with a key equaling the seconds the app was
launced at
 - find the maximum key of the set-the minimum key of the set/86400 to get
the number of days the app has been run over

This method will at least mean that if the user put's their clock back they
need to do that on a regular basis for it to work.

Cheers

Monte



More information about the use-livecode mailing list