1993-02-11 - Timed-Release Crypto

Header Data

From: corwin@Cayman.COM (Lord Among Panthers)
To: cypherpunks@toad.com
Message Hash: 73569d80b557b517326135b8fc4297b44edc5a6959aaee9c6a26e5a089e87ab0
Message ID: <9302112145.AA17000@cuba.Cayman.COM>
Reply To: <9302112058.AA03778@ptolemy.arc.nasa.gov>
UTC Datetime: 1993-02-11 21:46:35 UTC
Raw Date: Thu, 11 Feb 93 13:46:35 PST

Raw message

From: corwin@Cayman.COM (Lord Among Panthers)
Date: Thu, 11 Feb 93 13:46:35 PST
To: cypherpunks@toad.com
Subject: Timed-Release Crypto
In-Reply-To: <9302112058.AA03778@ptolemy.arc.nasa.gov>
Message-ID: <9302112145.AA17000@cuba.Cayman.COM>
MIME-Version: 1.0
Content-Type: text/plain

Robin  sez

>Dorn suggests: 
>>The servers would generate a key pair on request, for a fee.  Send you
>>the public key to encrypt the "message" for storage somewhere.  
> I guess this might work, but now you have to be more specific in
> telling your escrow service where to look for public keys to decode
> you message.  With just a few standard time-key servers, this isn't
> needed, and perhaps we could all share the costs of monitoring their
> trustworthyness.  Needing just a few, the need might easily be met by
> charity.

The escrow services could run the time-key servers (since without the time-key servers, there would be less business for the escrow services).  Getting keys
would then be free and the cost of running the server could be subsidised 
from the cost of storing the message.