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

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

#11156: "can't find a pluggable transport proxy" errors when obfsproxy started up
------------------------+--------------------------------
     Reporter:  asn     |      Owner:
         Type:  defect  |     Status:  needs_review
     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 nickm):

 If I'm not mistaken, on a client, two things can cause us to launch an OR
 connection: an attempt to fetch directory info, and an attempt to build a
 circuit for traffic.

 I believe that if should_delay_dir_fetches() is true, we won't try to
 launch any directory fetches.

 If we don't have enough directory info, then we won't try to build
 circuits, because router_have_minimum_dir_info() will return false.
 Also, if should_delay_dir_fetches() is true, we won't update
 have_minimum_dir_info in update_have_minimum_dir_info() [*], so even if we
 do have sufficient directory info in the cache, I believe we won't
 acknowledge that until should_delay_dir_fetches() returns false.

 So the approach above seems sound-ish to me.  I'm fine merging this patch
 if you've tested it, and it comes with a changes file.



 [*] We will need to update the notice message and status message that come
 from update_router_have_minimum_dir_info() when should_delay_dir_fetches()
 returns true.

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