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

Closed (moved)
(moved)
Open
Created Aug 01, 2012 by Zack Weinberg@zwol

Explicit "ORPort 0" should still trigger client mode

I have some scripts (which worked with 0.2.2.x) that explicitly specify "ORPort 0" in torrc files they generate for a Tor process that's meant to run in client mode. With 0.2.3.x, this seems to put the configuration parser into server mode, and then it bombs out because it doesn't like UseBridges=1 in server mode.

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