Re: [tor-bugs] #8864 [Tor]: Hidden service: Suddenly the service does not respond to new connections (INTRODUCE2 cell on intro circ with no corresponding rend_intro_point_t)

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#8864: Hidden service: Suddenly the service does not respond to new connections
(INTRODUCE2 cell on intro circ with no corresponding rend_intro_point_t)
------------------------+---------------------------------------------
     Reporter:  reiam   |      Owner:
         Type:  defect  |     Status:  needs_review
     Priority:  normal  |  Milestone:  Tor: 0.2.???
    Component:  Tor     |    Version:  Tor: 0.2.3.25
   Resolution:          |   Keywords:  tor-hs 023-backport 025-triaged
Actual Points:          |  Parent ID:
       Points:          |
------------------------+---------------------------------------------

Comment (by asn):

 Replying to [comment:25 nickm]:
 > I'd be okay if we just did this at latest time we could fetch a new
 consensus.  How hard/bad would that be?

 Hm, when is that I wonder?

 Clients download a new consensus every 1 hour, right? If yes, the latest
 time that an always-on client could have fetched a consensus would be its
 `valid-after` time + an hour? Or the time its published + an hour, if
 that's a different thing.

 > (And what's the harm of using an IP that's not in the consensus anyway?)

 Hm, good question.

 I guess the main issue is that clients with a newer consensus won't be
 able to use that IP. Or maybe the IP was found to be a bad relay?

 (There are not many nice attacks that IPs can launch right now, but maybe
 that will change in the future when we introduce scalability etc.)

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