aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-11-25 17:19:25 -0500
committerNick Mathewson <nickm@torproject.org>2012-12-17 14:51:31 -0500
commit4a07ea4a8c41c55ef4d8341ddf67601d3f09711a (patch)
tree050a2a73a7696419327a5ceadd9be9484bff4722 /changes
parent40a9842090fbf3ecbc155e5be11e200c9aef1a08 (diff)
downloadtor-4a07ea4a8c41c55ef4d8341ddf67601d3f09711a.tar
tor-4a07ea4a8c41c55ef4d8341ddf67601d3f09711a.tar.gz
Drop the maximum attempts to get a virtual address to 1000.
This is good enough to give P_success >= 999,999,999/1,000,000,000 so long as the address space is less than 97.95 full. It'd be ridiculous for that to happen for IPv6, and usome reasonable assumptions, it would also be pretty silly for IPv4.
Diffstat (limited to 'changes')
-rw-r--r--changes/ipv6_automap7
1 files changed, 7 insertions, 0 deletions
diff --git a/changes/ipv6_automap b/changes/ipv6_automap
index 150349c38..1b4458527 100644
--- a/changes/ipv6_automap
+++ b/changes/ipv6_automap
@@ -10,3 +10,10 @@
- AutomapHostsOnResolve responses are now randomized, to avoid
annoying situations where Tor is restarted and applications
connect to the wrong addresses.
+
+ - We never try more than 1000 times to pick a virtual address
+ when AutomapHostsOnResolve is set. That's good enough so long
+ as we aren't close to handing out our entire virtual address
+ space; if you're getting there, it's best to switch to IPv6
+ virtual addresses anyway.
+