[tor-bugs] #21816 [Core Tor/Tor]: Add support for Pluggable Transports 2.0

Tor Bug Tracker & Wiki blackhole at torproject.org
Sat Mar 25 11:22:49 UTC 2017


#21816: Add support for Pluggable Transports 2.0
--------------------------+----------------------------------
 Reporter:  chelseakomlo  |          Owner:
     Type:  enhancement   |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |        Version:  Tor: unspecified
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+----------------------------------

Comment (by iang):

 Sitting here in the session with darkk.  We think this is what needs
 changing:

 - transports.c already negotiates the PT protocol version number, and
 sticks it in a
   managed_proxy_t (field conf_protocol)

 - In connection.c, around line 2225, tor calls
 get_socks_args_by_bridge_addrport to get the socks
   args, but that doesn't give us a handle to the managed_proxy_t

 - So we should call find_transport_name_by_bridge_addrport to get the
 transport name

 - Then we'll need a new function in transports.c that's very much like
   get_managed_proxy_by_argv_and_type, except it's
 get_managed_proxy_by_transport_name
   (it searches the managed_proxy_list, and for each entry, searches the
 transports list looking
   for a match).  It also needs to be non-static.

 Then we'd be able to access the conf_protocol field in connection.c, and
 do the small changes to use the alternate SOCKS 5 authentication method
 specified in the PT 2.0 spec.

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


More information about the tor-bugs mailing list