From 16f2e4aa8ce76387c19687dd0c78c97929a852d6 Mon Sep 17 00:00:00 2001
From: Nick Mathewson <nickm@torproject.org>
Date: Tue, 12 Mar 2013 17:36:09 -0400
Subject: 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.
---
 changes/bug8427 | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 changes/bug8427

(limited to 'changes')

diff --git a/changes/bug8427 b/changes/bug8427
new file mode 100644
index 000000000..22b003fc3
--- /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.
-- 
cgit v1.2.3