[tor-bugs] #11156 [Tor]: "can't find a pluggable transport proxy" errors when obfsproxy started up

[Tor Bug Tracker & Wiki]

#11156: "can't find a pluggable transport proxy" errors when obfsproxy started up
------------------------+--------------------------------
     Reporter:  asn     |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-pt tor-client
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------------

Comment (by asn):

 Here is a better patch:
 {{{
 diff --git a/src/or/networkstatus.c b/src/or/networkstatus.c
 index 2b0242b..8fad960 100644
 --- a/src/or/networkstatus.c
 +++ b/src/or/networkstatus.c
 @@ -31,6 +31,7 @@
  #include "router.h"
  #include "routerlist.h"
  #include "routerparse.h"
 +#include "transports.h"

  /** Map from lowercase nickname to identity digest of named server, if
 any. */
  static strmap_t *named_server_map = NULL;
 @@ -888,7 +889,8 @@ update_consensus_networkstatus_fetch_time(time_t now)
  int
  should_delay_dir_fetches(const or_options_t *options)
  {
 -  if (options->UseBridges && !any_bridge_descriptors_known()) {
 +  if (options->UseBridges &&
 +      (!any_bridge_descriptors_known() ||
 pt_proxies_configuration_pending())){
      log_info(LD_DIR, "delaying dir fetches (no running bridges known)");
      return 1;
    }
 }}}

 Nick, opinions? How can we be sure that we are blocking all OR connections
 till the managed proxies have finished configuring?

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