Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #18582

Closed (moved)
(moved)
Open
Created Mar 20, 2016 by teor@teor

tor_addr_is_internal should never block PT dummy addresses

In #17674 (moved) and #8976 (moved), we block internal addresses when opening a connection.

In #18517 (moved), 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).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking