1994-08-09 - Key Coercion after encrypted message transmission.

Header Data

From: hughes@ah.com (Eric Hughes)
To: cypherpunks@toad.com
Message Hash: 7f4e40df798b8a4c54cbdea4eb26660f7e1ba0ca432de38f0b4e2460aab7bcf6
Message ID: <9408091635.AA22556@ah.com>
Reply To: <199408090533.AA06475@xtropia>
UTC Datetime: 1994-08-09 17:04:09 UTC
Raw Date: Tue, 9 Aug 94 10:04:09 PDT

Raw message

From: hughes@ah.com (Eric Hughes)
Date: Tue, 9 Aug 94 10:04:09 PDT
To: cypherpunks@toad.com
Subject: Key Coercion after encrypted message transmission.
In-Reply-To: <199408090533.AA06475@xtropia>
Message-ID: <9408091635.AA22556@ah.com>
MIME-Version: 1.0
Content-Type: text/plain


   I am not sure that there is a good way of addressing this
   problem short of dividing the key in some way among multiple people so
   that Darth has a hard time seizing them all. This idea has already
   been discussed elsewhere.

Remote backup and secret sharing, yes.

   This problem could be
   called the transmission retroactive coercion problem (TRCP). 

This one has also been discussed here, just last week, by me.  It's
the problem of forward secrecy.  It already has a perfectly good name,
thank you.

The original author of the message should find out what Diffie-Hellman
key exhange is and how it can be used for forward secrecy.

Eric





Thread