1994-08-09 - Remailer ideas

Header Data

From: hughes@ah.com (Eric Hughes)
To: cypherpunks@toad.com
Message Hash: d5bcdcf8552f869b6f530e074202f22c29e42648b467467a9e9863e00f18a693
Message ID: <9408091647.AA22577@ah.com>
Reply To: <9408091622.AA21758@netmail2.microsoft.com>
UTC Datetime: 1994-08-09 17:15:35 UTC
Raw Date: Tue, 9 Aug 94 10:15:35 PDT

Raw message

From: hughes@ah.com (Eric Hughes)
Date: Tue, 9 Aug 94 10:15:35 PDT
To: cypherpunks@toad.com
Subject: Remailer ideas
In-Reply-To: <9408091622.AA21758@netmail2.microsoft.com>
Message-ID: <9408091647.AA22577@ah.com>
MIME-Version: 1.0
Content-Type: text/plain


   multiplicative decreases in cutoff probability, and it is
   therefore easy to set a cutoff value for delay which will occur
   with sufficient infrequency as to be useless to the cryptanalyst.

They will be useless only as long as you have an assurance that these
cutoffs are not correlated with anything "too large" (left
deliberately hand-waving).

In particular, delivery times are related to the retry algorithms at
the higher level of the protocol.  These retry algorithms operate
between some two ends and therefore introduce correlations into the
message patterns.  It's not obvious (and may not be true) that
arbitrary latency limiting is a safe behavior.

   By "cryptanalysis," I mean traffic analysis.  Considering the
   remailers to be a cryptosystem was suggested recently on this list
   by someone (I forget whom).

That was me.  I'll have more to say on that subject later.

Eric





Thread