aboutsummaryrefslogtreecommitdiff
path: root/changes/bug6252_again
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-07-18 10:24:17 -0400
committerNick Mathewson <nickm@torproject.org>2012-07-18 10:24:17 -0400
commit393944dfb67fb27991e152ec67f74cebbf3a23ba (patch)
treebbc07516aa08e611f80a99d205489e54d7b98a7c /changes/bug6252_again
parentc1bd10411116c549326f74b09658a50bbae812b4 (diff)
downloadtor-393944dfb67fb27991e152ec67f74cebbf3a23ba.tar
tor-393944dfb67fb27991e152ec67f74cebbf3a23ba.tar.gz
Have the bug6252 commit message reflect its on-again/off-again status
Diffstat (limited to 'changes/bug6252_again')
-rw-r--r--changes/bug6252_again11
1 files changed, 11 insertions, 0 deletions
diff --git a/changes/bug6252_again b/changes/bug6252_again
new file mode 100644
index 000000000..f7fd00cb3
--- /dev/null
+++ b/changes/bug6252_again
@@ -0,0 +1,11 @@
+ o Security fixes:
+ - Tear down the circuit if we get an unexpected SENDME cell. Clients
+ could use this trick to make their circuits receive cells faster
+ than our flow control would have allowed, or to gum up the network,
+ or possibly to do targeted memory denial-of-service attacks on
+ entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
+ from July 2002, before the release of Tor 0.0.0. We had committed
+ this patch previously, but we had to revert it because of bug 6271.
+ Now that 6271 is fixed, this appears to work.
+
+