| commit | aa45e8259368c9733e459dc4f91f62492b9926da | |
| author | Nick Mathewson <nickm@torproject.org> | |
| Mon, 10 Jan 2011 22:24:16 +0000 (10 17:24 -0500) | ||
| committer | Nick Mathewson <nickm@torproject.org> | |
| Mon, 10 Jan 2011 22:24:16 +0000 (10 17:24 -0500) | ||
| tree | 19bbbe4cc88ced0cf4646999d0d5d64ecb77d88c | treesnapshot (tar.gz zip) |
| parent | 5ae391762c93fa4cdf47ceb24c31282daf695a65 | commitdiff |
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.
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.
| changes/bug2330 | [new file with mode: 0644] | blob |
| src/or/buffers.c | diffblobblamehistory |