1995-02-03 - Re: Frothing remailers - an immodest proposal

Header Data

From: Hal <hfinney@shell.portal.com>
To: cypherpunks@toad.com
Message Hash: f7d560da84bf5c2a6d156b885883e9daba3e1c999acecf7db9f026fc9cf4afbd
Message ID: <199502030225.SAA06856@jobe.shell.portal.com>
Reply To: N/A
UTC Datetime: 1995-02-03 02:26:30 UTC
Raw Date: Thu, 2 Feb 95 18:26:30 PST

Raw message

From: Hal <hfinney@shell.portal.com>
Date: Thu, 2 Feb 95 18:26:30 PST
To: cypherpunks@toad.com
Subject: Re:  Frothing remailers - an immodest proposal
Message-ID: <199502030225.SAA06856@jobe.shell.portal.com>
MIME-Version: 1.0
Content-Type: text/plain


One point re remailer reliability:  Even though in my discussions with
Nathan I did not really agree with his suggestion to have remailers check
signatures on incoming messages, actually Chaum did propose something
similar in his 1981 paper.

He would have each remailer sign the batch of messages it outputs each
cycle.  (Chaum's remailers used a straight batching approach.)  The idea,
as I recall, was to allow a remailer to prove that it had not engaged in
a denial-of-service attack by purposely dropping some message into the
bit bucket.  If some customer put his message in here and it didn't ever
come out over there, I guess the remailer could prove that it didn't lose
the message by showing its signed batch.  I'm not clear on the details
though.  Anyway, here is an area where message signing and reliability
have some intersection.

Hal





Thread