[tor-bugs] #3443 [Tor]: Client with low CBT can't establish any circuits

[Tor Bug Tracker & Wiki]

#3443: Client with low CBT can't establish any circuits
-----------------------------------+----------------------------------------
 Reporter:  arma                   |          Owner:                    
     Type:  defect                 |         Status:  new               
 Priority:  major                  |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor                    |        Version:                    
 Keywords:  regression tor-client  |         Parent:                    
   Points:                         |   Actualpoints:                    
-----------------------------------+----------------------------------------

Comment(by mikeperry):

 Replying to [comment:34 arma]:
 > Replying to [comment:33 mikeperry]:
 > > > (We just encountered this bug during our safer red-team analysis.
 Sad-face.)
 > >
 > > Do you know if it was because they changed guards/bridges, because TLS
 connections were being throttled, or if it was some other mystery factor?
 >
 > They ran their client using Tor-and-stegotorus-and-a-bridge, and then
 they switched to Tor-and-stegotorus-and-a-transparent-redirect-
 to-a-bridge.
 >
 > They're on the local deter testbed, so their client became convinced
 that 1500ms was a good timeout.

 Hrmm. I imagine the redirect didn't add measurable extra latency, nor did
 the bridge actually change..

 Sounds like that leaves connection setup as the most likely culprit,
 still? In which case, this could still be fixed by the changes mentioned
 in https://trac.torproject.org/projects/tor/ticket/3443#comment:22 and
 followups.

 I do like also deploying the hack you mention, too, just in case there are
 other issues. We definitely want that logline to be very descriptive of
 the tor client state, though.

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