Bill, I'm sure that anyone really determined to break such a scheme
will be able to do so, but a couple of ideas for making it a bit
harder occur to me:
1. Use some basic indirection - store the expiry date in one place,
and an md5 of it in another. If the expiry date gets changed, it will
no longer match the md5, and you'll know it's been changed.
2. Obscure the date. Generate a large random number and insert the
numerals that make up the date in a particular order and in
particular character positions within the random number.
3. Store the date as a custom property of a hidden control.
4. Encrypt the date with a key that you store on your server (so your
app has to grab it each time it checks the date, not so good if your
users launch your app while offline).
Best,
Mark
On 29 Dec 2008, at 22:30, Bill Vlahos wrote:
Mark,
Sure. It is for licensing. I was thinking that this would be a good
method for a limited time trial of my software. The document stack
would contain the user's data and the program would check the
creation date of the data stack for the trail period. Once the user
paid for the software it would no longer care what the creation
date was.
Bill
On Dec 29, 2008, at 12:59 PM, Mark Smith wrote:
Can I ask what the aim is? Is it a question of security? How
crucial is it? Bear in mind that with easily available tools, the
creation date in the filesystem itself can be altered.
Best,
Mark
On 29 Dec 2008, at 19:23, Bill Vlahos wrote:
Interesting idea. However, wouldn't that be similar to putting it
into a custom property? Someone could edit the script.
Bill
On Dec 29, 2008, at 12:01 AM, Jim Sims wrote:
On Dec 29, 2008, at 7:16 AM, Bill Vlahos wrote:
I would like to store a date stamp on a document stack when it
is created by my program in a way that can't be changed by the
user but that my program can examine.
set the script of btn "createDate" to the date
Does that work?
sims
[email protected]
Skype: sims.jim
iChat: techietours
______________________
Opportunity by Design
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
