[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Tracking Blocked Ports

To: or-dev@xxxxxxxxxxxxx
Subject: Re: Tracking Blocked Ports
From: Roger Dingledine <arma@xxxxxxx>
Date: Sun, 23 Nov 2008 19:55:38 -0500
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-dev-outgoing@xxxxxxxx
Delivered-to: or-dev@xxxxxxxx
Delivery-date: Sun, 23 Nov 2008 19:55:40 -0500
In-reply-to: <200810142316.17851.robert@xxxxxxxxxxxxxxx>
References: <200810142316.17851.robert@xxxxxxxxxxxxxxx>
Reply-to: or-dev@xxxxxxxxxxxxx
Sender: owner-or-dev@xxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

On Tue, Oct 14, 2008 at 11:16:12PM +0100, Robert Hogan wrote:
> Motivation:
> Tor clients that are behind extremely restrictive firewalls can end up waiting
> a while for their first successful OR connection to a node on the network.

Added as proposal 156:
https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/156-tracking-blocked-ports.txt
so we don't lose track of it.

My understanding is that the next step here is to a) decide if this
overall approach is the right approach, and b) revise the patch to be
more memory-friendly.

Thanks!
--Roger

Prev by Author: Re: draft proposal: download server descriptors on demand
Next by Author: determining which are the ORs a Tor circuit is using
Previous by thread: Re: [Announce] Introducing Tor VM – Tor in a virtual machine.
Next by thread: Re: Random note from TODO.021
Index(es):
- Author
- Thread