[tor-bugs] #28676 [Core Tor/Tor]: Tor versions of Tor nodes should be accessible through ControlPort

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Dec 3 07:45:40 UTC 2018


#28676: Tor versions of Tor nodes should be accessible through ControlPort
--------------------------+----------------------------------
 Reporter:  wagon         |          Owner:  arma
     Type:  enhancement   |         Status:  assigned
 Priority:  Medium        |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.4.9
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+----------------------------------

Comment (by wagon):

 > I'd like to build an abstraction layer over all available directory
 documents (like #25999, but inside tor).
 I have another idea. We have some trade-off between internal Tor's
 complexity and Tor's network performance. We need some balance which will
 make Tor support and development effective and convenient.

 Microdescriptors were added to Tor code long time ago (10 years?), when
 internet in general and Tor network in particular were 10-20 times slower
 than now (you can check metrics graphs). Amount of Tor nodes increased
 only 3 times during this period. Now we could remove this redundancy by
 moving to single type descriptors which will be not as small as
 microdescriptors but will be complete. We need de-duplication.

 Then, on top of these simplified descriptors you could make some
 abstraction layer for `ControlPort`. As concerns its current state, there
 are also other issues, e.g. with
 [[https://trac.torproject.org/projects/tor/ticket/28300#comment:4|status/version/num-{concurring,versioning}]]
 and with
 [[https://trac.torproject.org/projects/tor/ticket/28300#comment:6|"Option/*"]]
 values (I'm not sure I have to create separate tickets about that).

 P.S. I wonder why `ControlPort` can only be binded to loopback interface.
 Is it a bug or feature? I assume that in some environments, where Tor is
 controlled by a remote machine, it would be convenient to bind to another
 IP than 127.0.0.1 (firewall redirection can be used to overcome this
 difficulty, but direct binding is simpler to setup).

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


More information about the tor-bugs mailing list