aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-05-11 17:00:41 -0400
committerNick Mathewson <nickm@torproject.org>2012-05-11 17:16:29 -0400
commit35d08e30d89e5882b708a2cc6cb728f5393b2528 (patch)
treee07630bfeb3d681c04e9290ae53288e9308de7f1 /README
parent4bac2233116f0d94fd6ad1e77acb0baceeaf2336 (diff)
downloadtor-35d08e30d89e5882b708a2cc6cb728f5393b2528.tar
tor-35d08e30d89e5882b708a2cc6cb728f5393b2528.tar.gz
An attempt at bug3940 and making AllowDotExit 0 work with MapAddress
This time, I follow grarpamp's suggestion and move the check for .exit+AllowDotExit 0 to the top of connection_ap_rewrite_and_attach, before any rewriting occurs. This way, .exit addresses are forbidden as they arrive from a socks connection or a DNSPort request, and not otherwise. It _is_ a little more complicated than that, though. We need to treat any .exit addresses whose source is TrackHostExits as meaning that we can retry without that exit. We also need to treat any .exit address that comes from an AutomapHostsOnResolve operation as user-provided (and thus forbidden if AllowDotExits==0), so that transitioning from AllowDotExits==1 to AllowDotExits==0 will actually turn off automapped .exit addresses.
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions