Opened 7 years ago

Last modified 23 months ago

#6883 new project

Separate configuration options for separate Socks/NATD/Trans/DNS ports

Reported by: grarpamp Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.3.21-rc
Severity: Normal Keywords: tor-client configuration torrc options ports
Cc: Actual Points:
Parent ID: Points: 10
Reviewer: Sponsor:

Description

Various config, actions and policies such as...

trackhostexits
mapaddress
newnym
circuit/exit isolation
etc

have an affect on Tor as a whole. The recent addition
of multiple *Ports capability leads to the idea that
Tor could be extended capable of serving multiple
needs with one daemon. The only way to do this now
is with multiple daemons... which wouldn't take advantage
of certain shared knowledge, and is inefficient from
system resource and admin perspective.

Child Tickets

Change History (5)

comment:1 Changed 7 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: unspecified

I'm kicking this into "unspecified" for now. Individual options might be doable on a per-isolation-domain level, but trying to figure out every last thing that wants to go from global to per-port is going to be a pretty big amount of work, and we're pretty sure to miss stuff.

comment:2 Changed 7 years ago by nickm

Keywords: tor-client added

comment:3 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:4 Changed 2 years ago by nickm

Keywords: configuration torrc options ports added
Points: 10
Severity: Normal

I still think this is a pretty good idea, but also it's a lot of work.

comment:5 Changed 23 months ago by nickm

Summary: Roles for multiple Socks/NATD/Trans/DNS portsSeparate configuration options for separate Socks/NATD/Trans/DNS ports

Closed #12940 as a duplicate of this.

Note: See TracTickets for help on using tickets.