aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-11-14 23:35:55 -0500
committerNick Mathewson <nickm@torproject.org>2012-11-14 23:35:55 -0500
commitb1ad84dce61d11ffb0a3dff71ba404cf478e211c (patch)
tree46fc3191b0b5410104e9f7b086eccbfe1db99a2b
parent61d740ed0156e20d539bdfbe48b13a42167c2c8f (diff)
downloadtor-b1ad84dce61d11ffb0a3dff71ba404cf478e211c.tar
tor-b1ad84dce61d11ffb0a3dff71ba404cf478e211c.tar.gz
Add a changes file for IPv6 exits
-rw-r--r--changes/ipv6_exits18
1 files changed, 18 insertions, 0 deletions
diff --git a/changes/ipv6_exits b/changes/ipv6_exits
new file mode 100644
index 000000000..97af7512e
--- /dev/null
+++ b/changes/ipv6_exits
@@ -0,0 +1,18 @@
+ o Major features:
+
+ - Tor now has (alpha) support for exiting to IPv6 addresses. To
+ enable it as an exit node, make sure that you have IPv6
+ connectivity, 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 addresses only. On the client side, you'll need to
+ wait till the authorities have upgraded, wait for enough exits
+ to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
+ and use Socks5. Closes ticket 5547, implements proposal 117 as
+ revised in proposal 208.
+
+ We DO NOT recommend that clients with actual anonymity needs
+ start using IPv6 over Tor yet: not enough exits support it
+ yet, and there are some DNS-caching related issues that need
+ to be solved first.
+