Skip to content

GitLab

  • Menu
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 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • #1993

Closed
Open
Created Oct 01, 2010 by Robert Ransom@rransom

Documentation of BridgeRelay and PublishServerDescriptor is incorrect

The descriptions of the BridgeRelay and PublishServerDescriptor options in the tor(1) man page are no longer correct.

  • BridgeRelay is not ‘Usually used in combination with PublishServerDescriptor’ anymore, because the PublishServerDescriptor option is not in the sample torrc in the Tor distribution.
  • The main effect of the BridgeRelay option is now to cause a relay to publish a bridge descriptor to the bridge authority (rather than a relay descriptor to the public directory authorities), not to influence ‘how the relay will cache and serve directory information’.
  • Based on the syntax specified for PublishServerDescriptor, it appears to control publication of all things called descriptors -- not just relay descriptors, as the documentation suggests, but also bridge descriptors and hidden service descriptors.
  • In particular, the ‘hidserv’ flag to PublishServerDescriptor appears to be considered even for Tor instances that do not define ORPort.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking