Opened 3 years ago

Last modified 2 years ago

#20035 new enhancement

Identify client-specific options that work with hidden services

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: easy, doc, tor-hs tor-doc manual tor-client
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:2 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:3 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:4 Changed 2 years ago by nickm

Keywords: tor-doc manual tor-client added
Note: See TracTickets for help on using tickets.