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
  • #9651

Closed (moved)
(moved)
Open
Created 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
Time tracking