[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 timonh):

 Replying to [comment:27 akwizgran]:
 > 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.

 I discovered #19522 with Tor on Android switching from wifi to mobile
 data. See [https://trac.torproject.org/projects/tor/ticket/16387#comment:7
 #16387#comment:7].
 I noticed that Android kills all open connections when the network
 interface gets switched.
 Without #19522 the descriptor won't change because Tor would reconnect to
 the intro points.
 On which platform did you notice the behavior you describe?

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