summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2010-09-30 15:30:14 -0400
committerNick Mathewson <nickm@torproject.org>2010-09-30 15:30:14 -0400
commitd39e46c26d6992dcd019fa159981c057c3d24716 (patch)
treec37b2f965cbe2b017f46f0dae32a0eb7e6634b56 /changes
parent3ad43ef75f09a21c0c1fc6eb173f8d131c7d638c (diff)
parent5a19df1d94d8552a06dfc8fca9228dd36ed994e8 (diff)
downloadtor-d39e46c26d6992dcd019fa159981c057c3d24716.tar.gz
tor-d39e46c26d6992dcd019fa159981c057c3d24716.zip
Merge remote branch 'origin/maint-0.2.2'
Diffstat (limited to 'changes')
-rw-r--r--changes/bug19129
1 files changed, 9 insertions, 0 deletions
diff --git a/changes/bug1912 b/changes/bug1912
new file mode 100644
index 0000000000..5a7af756d1
--- /dev/null
+++ b/changes/bug1912
@@ -0,0 +1,9 @@
+ 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.