[tor-bugs] #3116 [Tor Client]: Notice how far our connections get; Report something useful about where they get stopped

[Tor Bug Tracker & Wiki]

#3116: Notice how far our connections get; Report something useful about where
they get stopped
-------------------------+--------------------------------------------------
 Reporter:  nickm        |          Owner:                    
     Type:  enhancement  |         Status:  new               
 Priority:  major        |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client   |        Version:                    
 Keywords:               |         Parent:                    
   Points:               |   Actualpoints:                    
-------------------------+--------------------------------------------------

Comment(by nickm):

 Replying to [comment:3 ioerror]:
 > Huh, really? That's funky.
 >
 > I think what we want is a way to simply log each line for important SSL
 transition states as we call it from the Tor source. This will give us a
 pretty good idea about what is failing and when.

 Sure, I agree that's a good start, but I think that we can do better.  The
 point of this ticket is that I'd like Tor to report a useful diagnostic by
 default if, say, all of our connections are dying in renegotiation, and
 not wait around for the user to configure debugging and extract the logs
 and send them to us.

 Here's an alternate option: instead of trying to answer "what's the
 farthest we've gotten" we could try to answer "where do connections get
 killed"?  In other words, when a connection times out or gets closed
 before the OR handshake is done, we could remember that, and report the
 totals if a while passes without our being able to build circuits.

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