diff options
| author | Nick Mathewson <nickm@torproject.org> | 2013-03-12 17:36:09 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2013-03-12 17:36:09 -0400 |
| commit | 16f2e4aa8ce76387c19687dd0c78c97929a852d6 (patch) | |
| tree | 3f289a6454fd81cfe9c8e0187021af5d3e417923 /changes/bug8427 | |
| parent | c6ca199888102a825f004f8613331f97525da486 (diff) | |
| download | tor-16f2e4aa8ce76387c19687dd0c78c97929a852d6.tar.gz tor-16f2e4aa8ce76387c19687dd0c78c97929a852d6.zip | |
Don't warn about not sending a socks reply if we get a write error
If we get a write error on a SOCKS connection, we can't send a
SOCKS reply, now can we?
This bug has been here since 36baf7219, where we added the "hey, I'm
closing an AP connection but I haven't finished the socks
handshake!" message. It's bug 8427.
Diffstat (limited to 'changes/bug8427')
| -rw-r--r-- | changes/bug8427 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/changes/bug8427 b/changes/bug8427 new file mode 100644 index 0000000000..22b003fc38 --- /dev/null +++ b/changes/bug8427 @@ -0,0 +1,5 @@ + o Minor bugfixes: + - If we encounter a write failure on a SOCKS connection before we + finish our SOCKS handshake, don't warn that we closed the + connection before we could send a SOCKS reply. Fixes bug 8427; + bugfix on 0.1.0.1-rc. |