Opened 12 years ago

Last modified 7 years ago

#603 closed enhancement (Won't implement)

option to specify minimal eligible speed for nodes used

Reported by: iar Owned by:
Priority: Low Milestone: post 0.2.0.x
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: iar, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I think it would be nice if I could set a bandwidth limit and/or average ping limit for my tor client.
For example I could ensure that all nodes to be used has 1Mbit or greater bandwidth. Its really slow to
have a 50Kbit node in the middle of two 4Mbit nodes...



[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (3)

comment:1 Changed 11 years ago by arma

Yeah, this is related to the Torflow project that Mike Perry and Fallon are
working on.

We're probably not going to let clients choose their own path constraints in
this way though, because that splinters the anonymity set too much. (If users
want much worse anonymity and slightly faster connections, they should go use
one of those commercial anonymizers.)

Worse, it looks like some of the new research attacks perform better on paths
that are much faster and higher bandwidth.

I'm going to close this as a 'won't implement', since we are working to make
Tor faster and better load balanced but this won't be one of the ways.

comment:2 Changed 11 years ago by arma

flyspray2trac: bug closed.

comment:3 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.