diff options
| author | Nick Mathewson <nickm@torproject.org> | 2013-03-20 16:17:06 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2013-03-20 16:17:06 -0400 |
| commit | fa3c23773944788125db2f67bcb048376c17fec9 (patch) | |
| tree | 93d89b2871e52c95ba5a9e5ae25817d44b0232ee /changes | |
| parent | a264c4fedab87ce7c8cbb94632657a90e95e7a4e (diff) | |
| download | tor-fa3c23773944788125db2f67bcb048376c17fec9.tar.gz tor-fa3c23773944788125db2f67bcb048376c17fec9.zip | |
Per-SOCKSPort configuration for bug 8117 fix.
This might be necessary if the bug8117 fix confuses any applications.
Also add a changes file.
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/bug8117 | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/changes/bug8117 b/changes/bug8117 new file mode 100644 index 0000000000..910e8056f4 --- /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. + + |