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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#11211: Multiple ServerTransportListenAddr entries should be allowed per transport.
----------------------------+----------------------------------
 Reporter:  yawning         |          Owner:
     Type:  defect          |         Status:  new
 Priority:  normal          |      Milestone:
Component:  Tor             |        Version:  Tor: unspecified
 Keywords:  tor-bridge, pt  |  Actual Points:
Parent ID:                  |         Points:
----------------------------+----------------------------------
 Looking through or/config.c, it is apparent that the
 ServerTransportListenAddr line only allows one address/port to be
 specified per transport.  This is problematic because there are cases
 where it is beneficial/required to list more than one.

 A simple example of where this would be useful is:
 {{{
 ServerTransportListenAddr obfs3 0.0.0.0:443
 ServerTransportListenAddr obfs3 [::]:443
 }}}

 The Pluggable Transport spec doesn't explicitly disallow having multiple
 bind addresses for TOR_PT_SERVER_BIND_ADDR, but I'm not sure what would
 happen if more than one is passed with each of the pt config protocol
 libraries in use.

     The keys holding transport names must appear on the same order
     as they appear on TOR_PT_SERVER_TRANSPORTS.

 Currently the particular example I used is probably a moot point because
 of #7961, but in general I don't see a good reason why each transport
 should be limited to one bind address.

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