aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2013-04-11 01:39:26 -0400
committerNick Mathewson <nickm@torproject.org>2013-04-11 01:39:55 -0400
commit7f50af116f2497a73fe9113e814a5765047cf3ca (patch)
tree8b31ff3c061a6978afb5438e52dc4b74124cf1c8 /changes
parent6acf0ac2851fb95953edea9c231d82f487f28c3d (diff)
parentfa3c23773944788125db2f67bcb048376c17fec9 (diff)
downloadtor-7f50af116f2497a73fe9113e814a5765047cf3ca.tar
tor-7f50af116f2497a73fe9113e814a5765047cf3ca.tar.gz
Merge remote-tracking branch 'public/bug8117_023' into maint-0.2.4
Conflicts: doc/tor.1.txt src/or/config.c src/or/connection.c
Diffstat (limited to 'changes')
-rw-r--r--changes/bug811713
1 files changed, 13 insertions, 0 deletions
diff --git a/changes/bug8117 b/changes/bug8117
new file mode 100644
index 000000000..910e8056f
--- /dev/null
+++ b/changes/bug8117
@@ -0,0 +1,13 @@
+ o Major bugfixes:
+
+ - Many SOCKS5 clients, when configured to offer a username/password,
+ offer both username/password authentication and "no authentication".
+ Tor had previously preferred no authentication, but this was
+ problematic when trying to make applications get proper stream
+ isolation with IsolateSOCKSAuth. Now, on any SOCKS port with
+ IsolateSOCKSAuth turned on (which is the default), Tor selects
+ username/password authentication if it's offered. If this confuses your
+ application, you can disable it on a per-SOCKSPort basis via
+ PreferSOCKSNoAuth. Fixes bug 8117; bugfix on 0.2.3.3-alpha.
+
+