1995-12-08 - Re: Still more on the Digicash protocol

Header Data

From: frantz@netcom.com (Bill Frantz)
To: Mark Twain Ecash Support <daw@delhi.CS.Berkeley.EDU (David A Wagner)
Message Hash: 8805feaf623668c0a887daeda45e1f7c1fa104452878ffaa165b712facd4fcec
Message ID: <199512081948.LAA16066@netcom15.netcom.com>
Reply To: N/A
UTC Datetime: 1995-12-08 19:50:12 UTC
Raw Date: Fri, 8 Dec 95 11:50:12 PST

Raw message

From: frantz@netcom.com (Bill Frantz)
Date: Fri, 8 Dec 95 11:50:12 PST
To: Mark Twain Ecash Support <daw@delhi.CS.Berkeley.EDU (David A Wagner)
Subject: Re: Still more on the Digicash protocol
Message-ID: <199512081948.LAA16066@netcom15.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain


At 12:26 12/8/95 -0600, Mark Twain Ecash Support wrote:
>DigiCash agrees that it is desirable to encrypt the payment request. The
>problem is how? You can't use the payor's public key, since the payor is
>anonymous to the payee. There are other, high overhead, protocols that might
>be used, but after taking MIM into account, securing the payment request
>from within Ecash while retaining acceptable latency is much harder to
>acomplish than one might think. 

Wouldn't a Diffie-Hellman key exchange work here?  Or is that too much overhead?


-----------------------------------------------------------------
Bill Frantz                   Periwinkle  --  Computer Consulting
(408)356-8506                 16345 Englewood Ave.
frantz@netcom.com             Los Gatos, CA 95032, USA







Thread