Opened 4 years ago
Closed 4 years ago
#18582 closed defect (wontfix)
tor_addr_is_internal should never block PT dummy addresses
| Reported by: | teor | Owned by: | |
|---|---|---|---|
| Priority: | Medium | Milestone: | Tor: 0.2.9.x-final |
| Component: | Core Tor/Tor | Version: | Tor: 0.2.7 |
| Severity: | Normal | Keywords: | comment-only easy |
| Cc: | Actual Points: | ||
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
In #17674 and #8976, we block internal addresses when opening a connection.
In #18517, we chose 192.0.2.0/24 as a dummy address range for Tor Browser to use for pluggable transports to use when they don't have the actual remote address.
Let's add a comment near the IPv4 range in tor_addr_is_internal_ to never block those addresses (or, if we do, to change how Tor Browser and PTs work first).
Child Tickets
Note: See
TracTickets for help on using
tickets.
We won't fix the issue this way, we're fixing the address check in #18517 instead.