summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-28 17:29:59 -0400
committerNick Mathewson <nickm@torproject.org>2011-04-26 23:54:16 -0400
commit4851de554d5fc473cc9418b15bfb752e45b7d81d (patch)
treeea71c8b607b82a17e72c4863f3f750afca73dba7 /changes
parente4689d840266088739eee39e9bef84e13c988ce9 (diff)
downloadtor-4851de554d5fc473cc9418b15bfb752e45b7d81d.tar.gz
tor-4851de554d5fc473cc9418b15bfb752e45b7d81d.zip
Do not automatically ignore Fast/Stable for exits when ExitNodes is set
This once maybe made sense when ExitNodes meant "Here are 3 exits; use them all", but now it more typically means "Here are 3 countries; exit from there." Using non-Fast/Stable exits created a potential partitioning opportunity and an annoying stability problem. (Don't worry about the case where all of our ExitNodes are non-Fast or non-Stable: we handle that later in the function by retrying with need_capacity and need_uptime set to 0.)
Diffstat (limited to 'changes')
-rw-r--r--changes/exitnodes_reliable7
1 files changed, 7 insertions, 0 deletions
diff --git a/changes/exitnodes_reliable b/changes/exitnodes_reliable
new file mode 100644
index 0000000000..62ef03a0ce
--- /dev/null
+++ b/changes/exitnodes_reliable
@@ -0,0 +1,7 @@
+ o Minor features:
+ - If ExitNodes is set, still pay attention to the Fast/Stable
+ status of exits when picking exit nodes. (We used to ignore
+ these flags when ExitNodes was set, on the grounds that people
+ who set exitnodes wanted all of those nodes to get used, but
+ with the ability to pick exits by country and IP range, this
+ doesn't necessarily make sense any more.)