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

Re: [tor-bugs] #3725 [Tor]: Implement the wildcard "*" protocol in {Client, Server}TransportPlugin lines

#3725: Implement the wildcard "*" protocol in {Client,Server}TransportPlugin lines
------------------------+--------------------------------
     Reporter:  asn     |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-client
Actual Points:          |  Parent ID:  #3591
       Points:          |
------------------------+--------------------------------

Comment (by dcf):

 Replying to [comment:8 asn]:
 > When Tor uses the wildcard transport in `TOR_SERVER_TRANSPORTS`, it also
 > places all the bindaddrs for all the transport it knows (from its
 > state file) to its `TOR_PT_SERVER_BINDADDR` environment variable. When
 the
 > transport proxy supports a transport that is also mentioned in the
 > `_BINDADDR` variable, it knows in which port to bind.

 This is the way I naturally interpreted the spec. You bind server ports
 that are
  1. listed in `TOR_PT_SERVER_BINDADDR`
  2. AND listed in `TOR_PT_SERVER_TRANSPORTS`
  3. AND are one of our supported transports.
 It's the intersection of three sets. When `TOR_PT_SERVER_TRANSPORTS=*`,
 you skip step 2 (i.e., intersect with the universe).

 https://gitweb.torproject.org/pluggable-
 transports/goptlib.git/blob/78e518c824d9541056ba2ca870df2bb01b810b05:/pt.go#l304

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