[tor-bugs] #16966 [Core Tor/Tor]: Better solution for an HS client descriptor cache entry to expire

Tor Bug Tracker & Wiki blackhole at torproject.org
Sat Jun 18 11:14:23 UTC 2016

#16966: Better solution for an HS client descriptor cache entry to expire
 Reporter:  dgoulet       |          Owner:
     Type:  enhancement   |         Status:  needs_information
 Priority:  Medium        |      Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  tor-hs        |  Actual Points:  2
Parent ID:                |         Points:  medium
 Reviewer:                |        Sponsor:
Changes (by asn):

 * actualpoints:   => 2


 Replying to [comment:4 dgoulet]:
 > Data point. Proposal 224 has a revision-counter in the descriptor so it
 fixes the expiring time issue.

 So the idea here is that when a client has no usable intro points from an
 HS descriptor, it refetches a descriptor, and if the received descriptor
 has a new revision-counter the client marks all intro points as retriable?

 Or simpler, everytime a client accepts a new HS descriptor, all enlisted
 intro points are marked as retriable regardless of their failure cache

 > Now, is adding that mechanism for the current protocol worth the work
 considering the current next generation effort?

 Hmm, I would go with "No, except if someone provides a nice patch". Let's
 save this mobile performance improvement for next gen hidden services :)

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16966#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

More information about the tor-bugs mailing list