aboutsummaryrefslogtreecommitdiff
path: root/src/or/connection_edge.h
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 /src/or/connection_edge.h
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 'src/or/connection_edge.h')
-rw-r--r--src/or/connection_edge.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/or/connection_edge.h b/src/or/connection_edge.h
index 70d0dd271..8ba2fafd0 100644
--- a/src/or/connection_edge.h
+++ b/src/or/connection_edge.h
@@ -62,6 +62,7 @@ int address_is_invalid_destination(const char *address, int client);
void addressmap_init(void);
void addressmap_clear_excluded_trackexithosts(or_options_t *options);
+void addressmap_clear_invalid_automaps(or_options_t *options);
void addressmap_clean(time_t now);
void addressmap_clear_configured(void);
void addressmap_clear_transient(void);