1994-06-10 - Re: Delayed self-encrypting messages

Header Data

From: Jim Gillogly <jim@rand.org>
To: Cypherpunks@toad.com
Message Hash: 53be7cec3a2a53692cf630c807440f3388ddd3d6abfba4410fc35c08d5feb43c
Message ID: <9406102032.AA14793@mycroft.rand.org>
Reply To: <199406102004.AA12160@crl.crl.com>
UTC Datetime: 1994-06-10 20:32:34 UTC
Raw Date: Fri, 10 Jun 94 13:32:34 PDT

Raw message

From: Jim Gillogly <jim@rand.org>
Date: Fri, 10 Jun 94 13:32:34 PDT
To: Cypherpunks@toad.com
Subject: Re: Delayed self-encrypting messages
In-Reply-To: <199406102004.AA12160@crl.crl.com>
Message-ID: <9406102032.AA14793@mycroft.rand.org>
MIME-Version: 1.0
Content-Type: text/plain



> Paul Schauble <pls@crl.com> writes:
> Can I do this with crypto technology? Can I send someone a message, and 
> possible a program, such that the message can only be decrypted after a 
> predetermined date?

I think you would need a trusted time server that sends out signed
timestamps... you can't trust other time sources, including WWV (just
broadcast a signal locally to swamp the signal).

Thread

• Return to June 1994

• Return to “hughes@ah.com (Eric Hughes)”
• Return to “Jim choate <ravage@bga.com>”
• Return to “Jim Gillogly <jim@rand.org>”

• Return to “Paul Schauble <pls@crl.com>”

• 1994-06-10 (Fri, 10 Jun 94 13:06:16 PDT) - Delayed self-encrypting messages - Paul Schauble <pls@crl.com>
  • 1994-06-10 (Fri, 10 Jun 94 13:32:34 PDT) - Re: Delayed self-encrypting messages - Jim Gillogly <jim@rand.org>
    • 1994-06-10 (Fri, 10 Jun 94 14:42:58 PDT) - Re: Delayed self-encrypting messages - Jim choate <ravage@bga.com>
  • 1994-06-11 (Fri, 10 Jun 94 17:01:50 PDT) - Delayed self-encrypting messages - hughes@ah.com (Eric Hughes)