[tor-bugs] #21453 [Core Tor/Tor]: add ClientTransportPlugin configuration to tor-service-defaults-torrc by default

[Tor Bug Tracker & Wiki]

#21453: add ClientTransportPlugin configuration to tor-service-defaults-torrc by
default
--------------------------+---------------------
 Reporter:  adrelanos     |          Owner:
     Type:  enhancement   |         Status:  new
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+---------------------

Comment (by arma):

 I think this is intended to be a ticket for the Tor deb?

 I think the suggested change is a fine idea, but I think we might want to
 work through the failure cases and make Tor handle them better. In
 particular, if the Tor deb added these ClientTransportPlugin lines, but it
 didn't require obfsproxy as a dependency, then everything would work fine
 until you add an obfs4 bridge, and then things would break, and there
 would be some mysterious log lines if you know how to look for log lines:
 {{{
 Feb 14 13:47:47.589 [warn] Could not launch managed proxy executable at
 '/usr/bin/obfs4proxy' ('No such file or directory').
 Feb 14 13:47:48.591 [warn] We were supposed to connect to bridge
 '18.18.18.18:443' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 }}}

 Are there good ways to handle the missing dependency in a more usable way?

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