aboutsummaryrefslogtreecommitdiff
path: root/changes/bug1345
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-05-13 16:59:31 -0400
committerNick Mathewson <nickm@torproject.org>2011-05-13 16:59:31 -0400
commitda8297dbcb6a44d2291878b01779500640e4d0b1 (patch)
tree969bb6b8fdb514dd6100b20e3e65bcc4df50ef7f /changes/bug1345
parenta3ae591115ba5c4a43ff4fa3839be274aac9e5c3 (diff)
downloadtor-da8297dbcb6a44d2291878b01779500640e4d0b1.tar
tor-da8297dbcb6a44d2291878b01779500640e4d0b1.tar.gz
Handle transitions in Automap*, VirtualAddrNetwork correctly
Previously, if they changed in torrc during a SIGHUP, all was well, since we would just clear all transient entries from the addrmap thanks to bug 1345. But if you changed them from the controller, Tor would leave old mappings in place. The VirtualAddrNetwork bug has been here since 0.1.1.19-rc; the AutomapHosts* bug has been here since 0.2.0.1-alpha.
Diffstat (limited to 'changes/bug1345')
-rw-r--r--changes/bug13456
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug1345 b/changes/bug1345
index b35e78f5e..0c9375a35 100644
--- a/changes/bug1345
+++ b/changes/bug1345
@@ -5,3 +5,9 @@
- When TrackHostExits is changed from a controller, remove any
mappings for hosts that should no longer have their exits tracked.
Bugfix on Tor 0.1.0.1-rc.
+ - When VirtualAddrNetwork option is changed from a controller,
+ remove any mappings for hosts that were automapped to
+ that network. Bugfix on 0.1.1.19-rc.
+ - When one of the AutomapHosts* options is changed from a
+ controller, remove any mappings for hosts that should no longer be
+ automapped. Bugfix on 0.2.0.1-alpha.