1997-09-26 - Re: Remailer Attack

Header Data

From: Alex de Joode <usura@sabotage.org>
To: cypherpunks@ssz.com
Message Hash: e338f02503af5a972e7b8cf280358a46ed995075c6422b9e28434b8c4f52272b
Message ID: <199709261114.NAA25455@basement.replay.com>
Reply To: N/A
UTC Datetime: 1997-09-26 11:50:27 UTC
Raw Date: Fri, 26 Sep 1997 19:50:27 +0800

Raw message

From: Alex de Joode <usura@sabotage.org>
Date: Fri, 26 Sep 1997 19:50:27 +0800
To: cypherpunks@ssz.com
Subject: Re: Remailer Attack
Message-ID: <199709261114.NAA25455@basement.replay.com>
MIME-Version: 1.0
Content-Type: text/plain



Anonymous sez:


: According to Raph's remailer stats, the remailers have widely varying
: latencies.  Given that only a few remailers have latencies which are
: acceptably low, the list of usable remailers is quite low.

: If the user of the remailer, Monty Cantsin for example, signs his
: messages, a fairly accurate measure of total transit time is obtained.
: The total transit time gives clues to the remailers which were
: actually used in the chain.  In an of itself, this may not comprise
: the user, but combined with other weaknesses it will cause the
: attacker to be significantly more confident of identification
: hypotheses.

: The remailers should all have about the same latency.  0 seconds seems
: like a good Schelling point.  What would it take to reduce remailer
: latency to under 60 seconds for most of the remailers?  Do people need
: old 486s to dedicate to the task?  Do they need money?  Better
: software?


Most remailers support a feature called 'latency', so one can
choose the latency one desires for a message.

ie:

::
Anon-To: username@host-name-here.nl
Latency: +00:00

This message will be remailed imediately, no queing etc.

--
  Alex de Joode | usura@SABOTAGE.ORG | http://www.sabotage.org
	Sabotage Internet: Your Internet Problem Provider.






Thread