aboutsummaryrefslogtreecommitdiff
path: root/changes/bug1912
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2010-09-30 17:32:17 -0400
committerRoger Dingledine <arma@torproject.org>2010-09-30 17:32:17 -0400
commitd62a2d6ee56eb70c3b52cff2c7f035e0aa8cc158 (patch)
tree1f270433f89ec18463e7b59df4b606a9154b143c /changes/bug1912
parent5a19df1d94d8552a06dfc8fca9228dd36ed994e8 (diff)
downloadtor-d62a2d6ee56eb70c3b52cff2c7f035e0aa8cc158.tar
tor-d62a2d6ee56eb70c3b52cff2c7f035e0aa8cc158.tar.gz
write up a changelog file
Diffstat (limited to 'changes/bug1912')
-rw-r--r--changes/bug19129
1 files changed, 0 insertions, 9 deletions
diff --git a/changes/bug1912 b/changes/bug1912
deleted file mode 100644
index 5a7af756d..000000000
--- a/changes/bug1912
+++ /dev/null
@@ -1,9 +0,0 @@
- o Major bugfixes:
- - When weighting bridges, we used to trust the bandwidths they provided
- in their descriptor, only capping them at 10MB/s. This turned out to be
- problematic for two reasons: Bridges could claim to handle a lot more
- traffic then they actually would, thus making more clients pick them and
- have a pretty effective DoS attack. The other issue is that new bridges
- that might not have a good estimate for their bw capacity yet would not
- get used at all unless no other bridges are available to a client.
- This fixes bug 1912; bugfix on 0.2.2.7-alpha.