From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,FORGED_HOTMAIL_RCVD2, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,fef40c7c6b003852 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Received: by 10.224.181.75 with SMTP id bx11mr3571530qab.7.1347693901143; Sat, 15 Sep 2012 00:25:01 -0700 (PDT) Received: by 10.52.90.129 with SMTP id bw1mr202801vdb.13.1347693901116; Sat, 15 Sep 2012 00:25:01 -0700 (PDT) Path: da15ni55818832qab.0!nntp.google.com!v8no3628195qap.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 15 Sep 2012 00:25:01 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=31.52.181.203; posting-account=pmkN8QoAAAAtIhXRUfydb0SCISnwaeyg NNTP-Posting-Host: 31.52.181.203 References: <7c39a531-1058-42de-9e56-f03f2b9f92dc@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <93b90c84-f6eb-41cc-bfea-ec87bbdecf3a@googlegroups.com> Subject: Re: Time Stamping Again. From: Austin Obyrne Injection-Date: Sat, 15 Sep 2012 07:25:01 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-09-15T00:25:01-07:00 List-Id: On Friday, September 14, 2012 10:10:17 PM UTC+1, bj=F6rn lundin wrote: > Den fredagen den 14:e september 2012 kl. 22:11:22 UTC+2 skrev Austin Obyr= ne: > On Friday, September 14, 2012 7:58:04 PM UTC+1, Simon Wright wrote: >= > > Many thanks - to me that's pretty conclusive. > Being accurate to one = second this is a usefull time stamp. Yes, hm, how about setting the compute= r clock to 1995-04-1 and change that source file. Then compile it again. Ve= ry useful time stamp ? Evidence of when it was changed? No, perhaps an indi= cator on what that particular computer's clock was set to at the time of ed= iting - nothing more ... /Bj=F6rn I guess there's nothing that can't be perverted in some way. This time stamp to my mind is a mutual datum that has potential use in E_co= mmerce (perhaps) as a tool in cases of non-repudiation of contracts made by= e_mail. I don't want to open another can of worms here but anything that lends itse= lf to non-repudiation of e-commerece can only be good. This requires a who= le "scheme" of methods that can quickly collate hard evidence for use in a = prosecution in law in the event of subsequent attempts at fraud. It requir= es more than just one stumbling block to fraud obviously, an entire arsenal= of traps against such fraud is needed.=20 Using numbered compilers (copies to trusted third parties like say conventi= onal solicitors) that are predated in a synchronised way is a starting poin= t at least. The entities would have to explain how the time stamp doesn't = coincide if they later try to change the numbered and timed agreement and p= urport it to be the original one. There's much more to this but time stamping of compilers to my mind is a us= eful start as a basic tool at least. Cheers - adacrypt