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

Re: [tor-bugs] #11301 [Tor]: Tor does not reconnect after network loss with bridges

#11301: Tor does not reconnect after network loss with bridges
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  nickm
  mikeperry              |     Status:  new
         Type:  defect   |  Milestone:  Tor: 0.2.???
     Priority:  major    |    Version:
    Component:  Tor      |   Keywords:  tor-client, tbb-usability, tbb-
   Resolution:           |  needs, 025-triaged, flashproxy, 025-deferrable,
Actual Points:           |  isis2015Q2
       Points:           |  Parent ID:
-------------------------+-------------------------------------------------

Comment (by arma):

 Replying to [comment:18 isis]:
 > The most reliable way that I know of to trigger it is to use normal
 relays as bridges

 That is an unsupported approach with known bugs. See e.g. #1776. I mean,
 feel free to do it, but when it breaks you get to keep the pieces. And I
 worry that people using this unsupported approach might be masking or
 distracting bugs in actual bridge use.

 > I remember vaguely looking into it and thinking that somewhere a list of
 available relays and another list of available bridges existed
 simultaneously, and then basically that the bridge list was either
 deduplicated or checked for normal relays, causing some or all of the
 "bridges" to end up back in the real relay list, and thus causing Tor to
 think that there weren't any of the configured bridges available.

 Sounds like you're describing #1776.

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