Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 325
    • Issues 325
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #18582
Closed
Open
Issue created Mar 20, 2016 by teor@teor

tor_addr_is_internal should never block PT dummy addresses

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

In legacy/trac#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