mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 21:23:58 +01:00
35d08e30d8
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.
6 lines
277 B
Plaintext
6 lines
277 B
Plaintext
o Major bugfixes:
|
|
- Change the AllowDotExit rules so they should actually work.
|
|
We now enforce AllowDotExit only immediately after receiving
|
|
an address via SOCKS or DNSPort: other sources are free to provide
|
|
.exit addresses after the resolution occurs.
|