Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,070
    • Issues 1,070
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 38
    • Merge Requests 38
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #30477

Closed
Open
Opened May 10, 2019 by Alexander Færøy@ahf🍍Owner

Tor should self-test reachability of TCP listeners exposed by PT's

It would be useful if Tor would do self-test of TCP port reachability for bridge listeners and not just the ORPort itself.

Currently when a bridge operator starts their Bridge Relay, Tor will test whether their ORPort is available from the internet, but we do not test the reachability of, for example, the obfs4 TCP port.

We believe that just testing for whether the port is available to the internet is better than to actually test if the port, for example, is able to speak the obfs4 protocol.

We should probably have a way to disable the warning that is emitted if a port is not reachable if, for example, the bridge is actually lying to Tor about its port, does not have a port, or the port is exposed via UDP instead of TCP.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Sponsor 30 - Objective 2.3
Milestone
Sponsor 30 - Objective 2.3
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/tor#30477