1992-10-20 - another service

Header Data

From: Eric Hollander <hh@soda.berkeley.edu>
To: cypherpunks@toad.com
Message Hash: a213894998668de417861789fbaefe97699e97a56f87e2d3099724679904950a
Message ID: <9210202353.AA04723@soda.berkeley.edu>
Reply To: N/A
UTC Datetime: 1992-10-20 23:53:46 UTC
Raw Date: Tue, 20 Oct 92 16:53:46 PDT

Raw message

From: Eric Hollander <hh@soda.berkeley.edu>
Date: Tue, 20 Oct 92 16:53:46 PDT
To: cypherpunks@toad.com
Subject: another service
Message-ID: <9210202353.AA04723@soda.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain



I have thought of another service, like the depository, which might be
useful to the user community:  a time stamping notary service.  This would
have less security problems than the depository and would also be neccessary
if RSA'ed documents are to replace contracts and other paper documents used
in business.

It would be easy to implement.  A machine is set up with a hardware random
number generator.  This is used to generate a time-stamp key pair, perhaps
every day or every hour.  A user sends a document to this computer, which
then signs it with the private half of the time-stamp key and then remails
it to the user.  Note that the document sent by the user is probably
already encrypted and/or signed; sending it to the time-stamper does not
compromise it in any way.

The time stamper also keeps publishing the public half of its keys, to a
wide enough audience that it would be impossible for any one person (or
Agency) to modify all of them.  Users could keep their own archives of
them.  After the time period has elapsed, the time-stamper should erase the
private key corresponding to the time period.  This is the only time that
trust is involved and that the system might be compromised.  If a private
key were leaked, a time-stamp could be forged.

This would allow users to keep dated, notarized documents in their files, so
they could later prove that they had certain information at a certain time.

Ideas?  Thoughts?

e





Thread