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

Header Data

From: futplex@pseudonym.com (Futplex)
To: cypherpunks@toad.com (Cypherpunks Mailing List)
Message Hash: 1633809960249c78a86e2b82502526d265248c9507ddc2ed612e723f1680fd8f
Message ID: <199512090738.CAA09330@opine.cs.umass.edu>
Reply To: <199512082234.OAA02297@ix9.ix.netcom.com>
UTC Datetime: 1995-12-09 07:37:36 UTC
Raw Date: Fri, 8 Dec 95 23:37:36 PST

Raw message

From: futplex@pseudonym.com (Futplex)
Date: Fri, 8 Dec 95 23:37:36 PST
To: cypherpunks@toad.com (Cypherpunks Mailing List)
Subject: Re: Still more on the Digicash protocol
In-Reply-To: <199512082234.OAA02297@ix9.ix.netcom.com>
Message-ID: <199512090738.CAA09330@opine.cs.umass.edu>
MIME-Version: 1.0
Content-Type: text/plain


Mark Twain Bank Ecash Support writes:
> 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. 

Bill Stewart writes:
# Obviously if the payer is the one transmitting the message, she doesn't
# use her public key to encrypt; hers would be used for signature if 
# appropriate.
# She should use the payee's public key, 
[...]

But the payment request is sent from the shop (payee) to the customer (payor).

-Futplex <futplex@pseudonym.com>
"Women need a reason to have sex; men just need a place" -from a fitness mag.




Thread