1998-01-19 - Onion routing

Header Data

From: ulf@fitug.de (Ulf =?iso-8859-1?Q?M=F6ller?=)
To: cypherpunks@toad.com
Message Hash: 226d700c2a1f081186e57e28f1f9c203995a205d80d47ce53c1022b6844f0fe0
Message ID: <19980119013252.18949@ulf.mali.sub.org>
Reply To: N/A
UTC Datetime: 1998-01-19 01:39:19 UTC
Raw Date: Mon, 19 Jan 1998 09:39:19 +0800

Raw message

From: ulf@fitug.de (Ulf =?iso-8859-1?Q?M=F6ller?=)
Date: Mon, 19 Jan 1998 09:39:19 +0800
To: cypherpunks@toad.com
Subject: Onion routing
Message-ID: <19980119013252.18949@ulf.mali.sub.org>
MIME-Version: 1.0
Content-Type: text/plain



To protect against timing analysis, Onion routing uses encrypted and
padded links, and the connection between the user and his local onion
router is assumed to be secure.

Obviously, padding offers protection against external adversaries
only.  The onion routers themselves know when an anonymous connection
is opened, how much data is transferred, and when it is closed.  So in
contrast to the mix net (where it is sufficient to use one honest mix
in a chain), honest onion routers that are used between two
cooperating onion routers do not offer additional protection.

Onion routers have a fixed number of neighbours.  If the first onion
router does not have any honest neighbours, there is no anonymity.
Generally, the maximal connected component of honest onion routers
forms the anonymity set.

Does that mean that every onion router needs to maintain many
encrypted links, or is there a more efficient solution?






Thread