summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-05-13 16:22:58 -0400
committerNick Mathewson <nickm@torproject.org>2011-05-13 16:28:50 -0400
commita3ae591115ba5c4a43ff4fa3839be274aac9e5c3 (patch)
tree7b0fd9a7c86faa3c5677a6c47aaa4e4ce78cf4df /changes
parentec81d17d0c03d73f4d4acd9102893113b2883d76 (diff)
downloadtor-a3ae591115ba5c4a43ff4fa3839be274aac9e5c3.tar.gz
tor-a3ae591115ba5c4a43ff4fa3839be274aac9e5c3.zip
When TrackExitHosts changes, remove all no-longer-valid mappings
This bug couldn't happen when TrackExitHosts changed in torrc, since the SIGHUP to reload the torrc would clear out all the transient addressmap entries before. But if you used SETCONF to change TrackExitHosts, old entries would be left alone: that's a bug, and so this is a bugfix on Tor 0.1.0.1-rc.
Diffstat (limited to 'changes')
-rw-r--r--changes/bug13455
1 files changed, 4 insertions, 1 deletions
diff --git a/changes/bug1345 b/changes/bug1345
index 6945b5fe17..b35e78f5e8 100644
--- a/changes/bug1345
+++ b/changes/bug1345
@@ -1,4 +1,7 @@
o Minor bugfixes:
- - On SIGHUP, do not clear out all TrackExitHost mappings, client DNS
+ - On SIGHUP, do not clear out all TrackHostExits mappings, client DNS
cache entries, and virtual address mappings: that's what NEWNYM is
for. Bugfix on Tor 0.1.0.1-rc; fixes bug 1345.
+ - 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.