mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-09-21 13:34:59 +02:00
da8297dbcb
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.
14 lines
743 B
Plaintext
14 lines
743 B
Plaintext
o Minor bugfixes:
|
|
- 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.
|
|
- 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.
|