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

Re: [tor-bugs] #27241 [Core Tor/Tor]: Extract information from more kinds of wedged directory connections.



#27241: Extract information from more kinds of wedged directory connections.
--------------------------+------------------------------------
 Reporter:  nickm         |          Owner:  nickm
     Type:  enhancement   |         Status:  needs_information
 Priority:  Medium        |      Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  fast-fix      |  Actual Points:
Parent ID:                |         Points:
 Reviewer:  mikeperry     |        Sponsor:  Sponsor8-can
--------------------------+------------------------------------

Comment (by mikeperry):

 Replying to [comment:6 nickm]:
 > Replying to [comment:5 mikeperry]:
 > > To help me understand the consequences of this (and to figure out if I
 need to also do anything here for #25573), I have the following questions:
 > >
 > > 3. When the dirconn is closed first (such as here or elsewhere in the
 code), where in the code do we decide to mark/clean up/close the
 corresponding linked edge conn? I could not find this..
 >
 > Hmm. I wonder if nothing closes it, actually. Can you think of some
 experiment we could do to find out?

 I am not sure. Do we have a way to trigger this bug?

 > > For #25573, I'm particularly concerned about multihop hsdir dirconns.
 But if we ever make regular directory activity multihop, this could apply
 there too. Plus the linked conn close conditions may be relevant to this
 bug?

 I've been digging and I still cannot find anything that closes the edge
 conn when it times out. This is fine for #25573, since it only deals with
 edge conns, but if we change that, we'll want to update #23373.

 For purposes of this bug, I think the only question that remains is if
 we've exposed  handle_response_fetch_microdesc() and
 router_load_extrainfo_from_string() to partial descriptors before.

 I think the dirconn closing issue can be an orthogonal bug.

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