1996-05-20 - Re: The Crisis with Remailers

Header Data

From: “E. ALLEN SMITH” <EALLENSMITH@ocelot.Rutgers.EDU>
To: loki@infonex.com
Message Hash: 4fed8ec1de7950acec7b277e943c58d849f34084e1dbf77adaead9f8feeab946
Message ID: <01I4WVQJYM428Y5FKU@mbcl.rutgers.edu>
Reply To: N/A
UTC Datetime: 1996-05-20 11:49:22 UTC
Raw Date: Mon, 20 May 1996 19:49:22 +0800

Raw message

From: "E. ALLEN SMITH" <EALLENSMITH@ocelot.Rutgers.EDU>
Date: Mon, 20 May 1996 19:49:22 +0800
To: loki@infonex.com
Subject: Re: The Crisis with Remailers
Message-ID: <01I4WVQJYM428Y5FKU@mbcl.rutgers.edu>
MIME-Version: 1.0
Content-Type: text/plain


From:	IN%"loki@infonex.com" 18-MAY-1996 20:02:12.04

>I was invited to the digicash API design meeting precisely to make sure it
>could be used in remailers. It will not be using the current API. The
>problem is that Mixmaster requires exact knowledge of the size of every
>object in the message, to maintain constant message size. I could set aside
>room for one, two, three coins, but there is no guarantee that the payment
>will be made with only that many coins. The current API is going to be high
>level. It will does not allow the program to know anything about the
>internals of the payment. I need to be able to specify payment of amount X
>using no more than N coins. As soon as I have that level of control, you
>will see postage in Mixmaster.

	Good. I can see doing a limited postage now, actually, with relatively
simple modifications - the postage goes to the initial remailer front end and
to the remailer that sends out the message to something other than another
remailer.
	-Allen





Thread