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 319
    • Issues 319
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 37
    • Merge requests 37
  • 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
  • #20035
Closed
Open
Created Aug 31, 2016 by teor@teor

Identify client-specific options that work with hidden services

Many of the "client-specific" options in the tor manual page work with Hidden Services.

Others, such as Socks/Trans/NATD/DNSPort, do not.

It would be great to split up the client-only section into those options that truly only work for clients, and those that also affect the behaviour of hidden services (and bridge relays, and relays, and authorities).

For example, when a bridge relay builds an anonymous 3-hop path to submit its descriptor, it is likely affected by all the client options that affect node selection. (Unless we specifically disable them for servers.)

And a hidden service's paths are affected by these same options.

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