Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!alberta!cpsc.ucalgary.ca!datapsan!dataspan!richard From: richard@dataspan.dataspan.UUCP (Richard "Tiger" Melville) Newsgroups: comp.unix.internals Subject: Re: Preventing date rollback Message-ID: Date: 5 Dec 90 21:55:55 GMT References: Sender: richard@datapsan.UUCP Followup-To: comp.unix.internals Distribution: comp Organization: DataSpan Technology Inc., Calgary, Alberta, Canada Lines: 21 In-reply-to: rcosj@chudich.co.rmit.oz's message of 4 Dec 90 22:08:57 GMT In article rcosj@chudich.co.rmit.oz (John Simmons) writes: >Is there a reliable way to test if the date on a machine has been rolled >back ? Couldn't you get your program to check the date fairly regularly when it is run and write it away somewhere, keeping track of the latest date reached so far, then refuse to run at any time/date earlier than the latest one stored. I considered this, but all that is required to get around it is to re-install the software, and our record of the date is gone. I am wondering if I just shouldn't touch the guy's .login or some other frequently found but seldom modified file, and use that for my record of the date. Then, if the date of that file is ever found to be in the future, the date has been rolled back. Not foolproof, of course, but perhaps something along these lines could work most of the time... -- _Q Q_ Richard Melville DataSpan Technology Inc. __ /_\) /| 237-9313 400-540 5th ave SW _\___/O____O|/O____/ \_ Calgary Alberta Canada, T2P 0M2 _/ \_