Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #9651

Closed (moved)
Open
Opened Sep 03, 2013 by George Kadianakis@asn

Enable ExtORPort by default when PTs are used?

When we merged the Extended ORPort to tor.git (#4773 (moved) and #5040 (moved)), I wrote a post to tor-relays asking people to upgrade to git master so that they can get statistics with their bridge (https://lists.torproject.org/pipermail/tor-relays/2013-August/002477.html).

Unfortunately, I forgot to ask people to enable the Extended ORPort in their torrc, so their Tor just opens an ORPort and all their obfsproxy traffic goes through there.

Currently, the Extended ORPort can be enabled by adding ExtORPort 6669 to your torrc.

This is OK for now, but maybe we could make Tor smarter and make it open an Extended ORPort if it has an ORPort && there is a ServerTransportPlugin present in its torrc.

(With the above logic, if the bridge has a ServerTransportPlugin but with an older obfsproxy that doesn't support the Extended ORPort, then the ExtORPort will be left unused. That shouldn't be a big problem since the Extended ORPort is only bound on localhost.)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.5.x-final
Milestone
Tor: 0.2.5.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#9651