Howard Bornstein wrote:

I use an effective method of timing out software that isn't vulnerable
to turning back the system date and doesn't rely on a data file. I
check a system directory that is updated by access to the web (e.g. a
directory that's a repository for internet cookies). In most companies
these days, people access the interenet every day. Thus, there is
almost always a file that's been created in that directory each day. I
check the creation date of the latest file as my check file for the
current date and compare that against the timeout date.


Why is that not "vulnerable to turning back the system clock" ?
If I set my system clock to a year ago, then each time I access the web, I'll create my cookie files with dates in 2004.


--
Alex Tweedly       http://www.tweedly.net



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 15/03/2005

_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to