summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-01-10 17:24:16 -0500
committerNick Mathewson <nickm@torproject.org>2011-01-10 17:24:16 -0500
commitaa45e8259368c9733e459dc4f91f62492b9926da (patch)
tree19bbbe4cc88ced0cf4646999d0d5d64ecb77d88c /changes
parent5ae391762c93fa4cdf47ceb24c31282daf695a65 (diff)
downloadtor-aa45e8259368c9733e459dc4f91f62492b9926da.tar.gz
tor-aa45e8259368c9733e459dc4f91f62492b9926da.zip
Pull up more data when parsing socks messages
Previously, we only looked at up to 128 bytes. This is a bad idea since socks messages can be at least 256+x bytes long. Now we look at up to 512 bytes; this should be enough for 0.2.2.x to handle all valid SOCKS messages. For 0.2.3.x, we can think about handling trickier cases. Fixes 2330. Bugfix on 0.2.0.16-alpha.
Diffstat (limited to 'changes')
-rw-r--r--changes/bug23307
1 files changed, 7 insertions, 0 deletions
diff --git a/changes/bug2330 b/changes/bug2330
new file mode 100644
index 0000000000..fc0c4d8c36
--- /dev/null
+++ b/changes/bug2330
@@ -0,0 +1,7 @@
+ o Minor bugfixes
+ - Handle SOCKS messages longer than 128 bytes long correctly, rather
+ than waiting forever for them to finish. Fixes bug 2330. Bugfix on
+ 0.2.0.16-alpha. Found by doorss.
+
+
+