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

Re: [tor-bugs] #7733 [Tor]: Two channels required for bootstrap

#7733: Two channels required for bootstrap
------------------------+-----------------------------------------------
     Reporter:  dcf     |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-client flashproxy 025-triaged
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-----------------------------------------------

Comment (by nickm):

 I can almost reproduce this, modulo other annoying startup bugs (eg
 #9229).

 (I don't have a working flashproxy setup handy, so I tried adding a log
 message to channel_tls_connect() to let me know when it was invoked.  Then
 I started with a single bridge *without* a configured identity.  When it
 started with full directory information, it called channel_tls_connect()
 twice: once with a null ID, and once with the real ID from the cached
 bridge descriptor.  So, I can try to fix _that_, though I don't think
 that's necessarily the issue here.)

 Can the behavior on this ticket be reproduced without a pluggable
 transport?  In particular, I want an easy reproducible way to make Tor
 launch the two channels as described here.

 I'm attaching the small patch that makes us log new TLS channels at
 NOTICE.

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