[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #19859 [Core Tor/Tor]: Expose stream isolation information to controllers

#19859: Expose stream isolation information to controllers
-------------------------------------------------+-------------------------
 Reporter:  nickm                                |          Owner:  (none)
     Type:  enhancement                          |         Status:  new
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  unspecified
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:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by JeremyRand):

 Tor patch at https://notabug.org/JeremyRand/tor/src/stream-socks-auth (Git
 commit hash 5c57583ad3efbaf711ce9a1b967ccfbac1db9e1d).

 I ended up going with Nick's option (1), for the following reasons:

 1. It keeps the Tor patch simple, and allows the controller (which is
 written in a higher-level language  (Python in my case) and is therefore
 less prone to memory safety bugs) to handle the isolation logic.
 2. For performance reasons, Namecoin needs to preemptively open
 connections before the STREAM events are received.  So whatever isolation
 data the controller receives will be used to assign resolution commands to
 existing Namecoin connections; this limits the applicability of Nick's
 option (4).
 3. There's already precedent for this in the `CIRC` event (which sends the
 stream isolation data fields verbatim), and it seems weird to make the
 `STREAM` event have a wildly different design than the `CIRC` event for
 the same functionality.

 I infer from the keywords on this ticket that you'll also want a spec
 patch; is that correct?  Is there anything else needed for this?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19859#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs