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

Re: [tor-bugs] #25882 [Core Tor/Tor]: clients not detecting stale onion service introduction points

#25882: clients not detecting stale onion service introduction points
-------------------------------------------------+-------------------------
 Reporter:  cypherpunks                          |          Owner:  (none)
     Type:  defect                               |         Status:  closed
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  unspecified
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:  fixed
 Keywords:  tor-hs, reachability, network-team-  |  Actual Points:
  roadmap-september                              |
Parent ID:  #30200                               |         Points:
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor27-must
-------------------------------------------------+-------------------------
Changes (by dgoulet):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Soooo we've done lots of fixes in the HS subsystem lately regarding
 circuit timeouts.

 Specifically, I think client side, these two tickets will prevent the
 client to open dozens of intro circuit that is not working: #31541 and
 #32020.

 We did a series of fixes also service side: #32094, #31652, #31632

 As of the long term solution, I believe "Proposal A" from above: #27842

 Now there seems to be a final point in this ticket about making a client
 to claim that an IP failed if the RP never connected as in handle the
 `CIRCUIT_PURPOSE_C_REND_READY_INTRO_ACKED` purpose when cleaning up a
 circuit. I think that we could do a counter here and at least allow the
 client to retry to the IP with another RP and if after like 2 or 3 times
 the circuit always fail in state
 `CIRCUIT_PURPOSE_C_REND_READY_INTRO_ACKED`, considering the IP bad seems
 legitimate since either the service is not connecting properly or the IP
 is not relaying.

 I have created #32614 for this one ^.

 I believe we have tickets for each action items in this ticket so I'm
 going to close it. Please point out anything missing, ideally with a fresh
 ticket clearly explaining what is the issue and possible solutions if any.

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