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

Re: [tor-bugs] #11211 [Core Tor/Tor]: Multiple ServerTransportListenAddr entries should be allowed per transport.

#11211: Multiple ServerTransportListenAddr entries should be allowed per transport.
-------------------------------------------------+-------------------------
 Reporter:  yawning                              |          Owner:  kaie
     Type:  enhancement                          |         Status:
                                                 |  needs_revision
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.0.x-final
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  unspecified
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-bridge, pt, needs-proposal,      |  Actual Points:
  tor-pt, bridgedb-parsers, 028-triage, ipv6,    |
  tor-03-unspecified-201612                      |
Parent ID:  #10629                               |         Points:
 Reviewer:                                       |        Sponsor:  T/U
-------------------------------------------------+-------------------------

Comment (by kaie):

 Yawning, I think your opinion matters, because you are the expert in this
 area and are providing review feedback.

 The question is, how important is it to have this enhancement, and how
 could it be implemented with available resources?

 If the ideal solution that you describe is the only acceptable solution,
 then I most likely won't be able to find enough time to help, and the
 feature needs to be delayed, until enough developer time resources are
 available.

 However, if the feature is sufficiently important to not wait for the
 ideal implementatiom, but accept a simpler solution, then it's easier to
 find the time to get it done, and maybe I'll be able to help.

 So, it's interesting to get more feedback, if the suggested alias solution
 seems like an acceptable implementation, or if there are good arguments to
 reject that approach, too.

 Regarding BridgeDB registration: If Tor is the software that handles the
 registration into the BridgeDB, then the Tor software knows for which
 aliases a ListenAddr has been registered, and which transport type is used
 for each ListenAddr, and should be able to register accordingly?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11211#comment:28>
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