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

Re: [tor-bugs] #18620 [Core Tor/Tor]: HSFORGET command to clear cached client state for a HS

#18620: HSFORGET command to clear cached client state for a HS
-------------------------------------------------+-------------------------
 Reporter:  str4d                                |          Owner:  str4d
     Type:  enhancement                          |         Status:
 Priority:  Medium                               |  needs_revision
Component:  Core Tor/Tor                         |      Milestone:  Tor:
 Severity:  Normal                               |  0.2.9.x-final
 Keywords:  tor-hs, 029-accepted, review-        |        Version:  Tor:
  group-3                                        |  0.2.7.6
Parent ID:                                       |     Resolution:
 Reviewer:  asn, special                         |  Actual Points:
                                                 |         Points:  1
                                                 |        Sponsor:
                                                 |  SponsorR-can
-------------------------------------------------+-------------------------

Comment (by akwizgran):

 Replying to [comment:25 timonh]:
 > I think this is connected to #19522. If a HS changes it's ip address and
 choses new intro point because of #19522 then a client with a cached
 descriptor will retry the old intro points before fetching the descriptor
 again.

 Thanks for pointing out the related issue - you're right that this is
 related to clients caching descriptors for services with unstable
 connectivity.

 I'm not sure whether a solution to #19522 would necessarily fix this
 issue. We need to consider not just situations where the service's network
 interface is down, but also situations where one interface goes down and
 another comes up (for example, switching from mobile data to wifi). In
 that case the service can create a new set of introduction point circuits
 and publish a new descriptor via the new network interface while the old
 interface remains down, so returning to the old circuits when the old
 interface comes back up would not solve the problem.

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