diff options
author | Nick Mathewson <nickm@torproject.org> | 2011-07-19 20:43:28 -0400 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2011-07-19 20:43:28 -0400 |
commit | 195bcb6150eeaebab31a44998e2c567d78f9b936 (patch) | |
tree | 6a7705032e8f35775bdc573943103fba4ea3cd2e /changes | |
parent | 553ae5dfb5f6bb49889b2b1735217dae803f92d7 (diff) | |
parent | 1017322b59c5c722b1db4e2f040db5cceb41dea9 (diff) | |
download | tor-195bcb6150eeaebab31a44998e2c567d78f9b936.tar.gz tor-195bcb6150eeaebab31a44998e2c567d78f9b936.zip |
Merge remote-tracking branch 'public/prop171_v2'
Diffstat (limited to 'changes')
-rw-r--r-- | changes/prop171 | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/changes/prop171 b/changes/prop171 new file mode 100644 index 0000000000..91c463f94d --- /dev/null +++ b/changes/prop171 @@ -0,0 +1,22 @@ + o Major features: + - You can now configure Tor so that streams from different + applications are isolated on different circuits, to prevent an + attacker who sees your streams leaving an exit node from linking + your sessions to one another. To do this, choose some way to + distinguish the applications -- have them connect to different + SocksPorts, or have one of them use SOCKS4 while the other uses + SOCKS5, or have them pass different authentication strings to + the SOCKS proxy. Then use the new SocksPort syntax to configure + the degree of isolation you need. This implements Proposal 171. + + o Minor features: + - There's a new syntax for specifying multiple client ports (such as + SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare + multiple ...Port entries with full addr:port syntax on each. + The old ...ListenAddress format is still supported, but you can't + mix it with the new SOCKSPort syntax. + + o Code simplifications and refactoring: + - Rewrote the listener-selection logic so that parsing which ports + we want to listen on is now separate form binding to the ports + we want. |