[Whonix-devel] #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 adrelanos):

 Replying to [comment:1 arma]:
 > I think this is intended to be a ticket for the Tor deb?

 Yes. However, I guess the Tor source package ships also a {{{tor-service-
 defaults-torrc}}}?

 > 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?

 The same would happen if the user just added a ClientTransportPlugin line
 as well as an an obfs4 bridge but forgot to install obfs4proxy package. Is
 this perhaps worth a separate ticket and not a blocker here?

 Another option is to shift responsibility on the related packages, i.e.
 obfs4proxy and fteproxy. Tell them to wait for Tor feature
 {{{torrc.d-style configuration directories}}} (#1922) and then ship an
 {{{/etc/torrc.d}}} config snippet?

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