1997-06-25 - Re: Anonymous browsing (was Re: Getting Back to our Radical Roots)

Header Data

From: Lucky Green <shamrock@netcom.com>
To: Jeremey Barrett <jeremey@bluemoney.com>
Message Hash: 6c8dc18a31556ef4499b59e490fceb291d2b9f9a1d5f2958d0cf7569be0965da
Message ID: <Pine.3.89.9706251552.A12831-0100000@netcom2>
Reply To: <3.0.1.32.19970625153558.00840200@descartes.bluemoney.com>
UTC Datetime: 1997-06-25 23:04:42 UTC
Raw Date: Thu, 26 Jun 1997 07:04:42 +0800

Raw message

From: Lucky Green <shamrock@netcom.com>
Date: Thu, 26 Jun 1997 07:04:42 +0800
To: Jeremey Barrett <jeremey@bluemoney.com>
Subject: Re: Anonymous browsing (was Re: Getting Back to our Radical Roots)
In-Reply-To: <3.0.1.32.19970625153558.00840200@descartes.bluemoney.com>
Message-ID: <Pine.3.89.9706251552.A12831-0100000@netcom2>
MIME-Version: 1.0
Content-Type: text/plain



On Wed, 25 Jun 1997, Jeremey Barrett wrote:

> The trick is to design a system where an eavesdropper can't correlate
> a connection into the anonymous network to one coming out. Such a system will 
> 
> almost certainly involve some sort of "personal proxy" running on your own 
> machine. It might maintain a constant bandwidth to the anonymous network, but 
> 
> that's sub-optimal since most people like their bandwidth for other things.

The trick for users might be to move everything through the DC net. That way 
you take a max. hit of 50% loss of bandwidth. The problem would likely be 
worse for intermediate nodes. Need to think about this some more. There 
is a solution...

--Lucky






Thread