[tor-bugs] #19859 [Core Tor/Tor]: Expose stream isolation information to controllers
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Oct 9 23:15:35 UTC 2019
#19859: Expose stream isolation information to controllers
-------------------------------------------------+-------------------------
Reporter: nickm | Owner: (none)
Type: enhancement | Status:
| needs_revision
Priority: Medium | Milestone: Tor:
| 0.4.3.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-hs tor-control dns isolation | Actual Points:
needs-spec needs-design term-project |
Parent ID: | Points: 3
Reviewer: nickm | Sponsor:
-------------------------------------------------+-------------------------
Comment (by JeremyRand):
Thanks for the review Nick!
> So what if, instead of having a bunch of different ISOLATE_XYZ flags, we
have one item that is a comma-separated list of entries flags, each
matching the name of one of the other fields?
If I'm understanding you correctly, you're suggesting having an
`ISO_FIELDS` field, such that `ISO_FIELDS=FOO,BAR` means that the `FOO`
and `BAR` fields of the `STREAM` event represent fields that the SOCKS
port is configured to isolate on? I think this is a good idea, but there
is a caveat. Tor can isolate based on destination address, destination
port, and client address, but those don't have a 1:1 correspondence to
`STREAM` fields (they're components of fields that contain both an address
and a port). So in order for this to work, I'd need to add 3 additional
fields to `STREAM` events that are arguably redundant. Is that
acceptable?
Agreed on the other spec suggestions.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19859#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list