diff options
| author | Roger Dingledine <arma@torproject.org> | 2013-10-10 21:17:19 -0400 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2013-10-10 21:17:19 -0400 |
| commit | eb5d75e96afed76b968cb87365ba6e54cac35b2e (patch) | |
| tree | 9225d25c56abb0b394ddbc8f9836da6d0423f2f3 /ChangeLog | |
| parent | 2c7ed0406f04caa1609014f66c08964c8b38d0b9 (diff) | |
| download | tor-eb5d75e96afed76b968cb87365ba6e54cac35b2e.tar.gz tor-eb5d75e96afed76b968cb87365ba6e54cac35b2e.zip | |
rewrite history to improve two changelog entries
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 5 |
1 files changed, 2 insertions, 3 deletions
@@ -308,8 +308,7 @@ Changes in version 0.2.4.7-alpha - 2012-12-24 network connection drastically changes. Should help with bug 3443. o Major features (IPv6): - - Tor now has (alpha) support for exiting to IPv6 addresses. To - enable it as an exit node, make sure that you have IPv6 + - Relays can now exit to IPv6 addresses: make sure that you have IPv6 connectivity, then set the IPv6Exit flag to 1. Also make sure your exit policy reads as you would like: the address * applies to all address families, whereas *4 is IPv4 address only, and *6 is IPv6 @@ -779,7 +778,7 @@ Changes in version 0.2.4.3-alpha - 2012-09-22 than it ran through the part of the loop before it had made its choice. Addresses ticket 6538. - Disable the use of Guard nodes when in Tor2WebMode. Guard usage - by tor2web clients allows hidden services to identity tor2web + by tor2web clients allows hidden services to identify tor2web clients through their repeated selection of the same rendezvous and introduction point circuit endpoints (their guards). Resolves ticket 6888. |