Opened 8 days ago

Last modified 8 days ago

#26769 new defect

We should make HSv3 desc upload less frequent

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs network-health easy hsdir
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Without checking the source code right now, HSDirs are supposed to cache HS descriptors for the inscribed lifetime (3 hours), and HSv3s are supposed to upload descriptors at a random time between 1 and 2 hours (see HS_SERVICE_NEXT_UPLOAD_TIME_MIN).

This makes HSv3s upload descriptors more frequently than needed. For example, we could increase this to upload descriptors between 2 and 2.9 hours, to make HSv3s less intense on the network.

Someone should double check the above logic and make sure it won't cause issues, and implement it.

Child Tickets

Change History (1)

comment:1 in reply to:  description Changed 8 days ago by arma

Replying to asn:

This makes HSv3s upload descriptors more frequently than needed. For example, we could increase this to upload descriptors between 2 and 2.9 hours, to make HSv3s less intense on the network.

The main reason v2 onion services uploaded so frequently (way more frequently than this) is to handle relays that restart (and thus discard all of their onion service descriptors) and relays that rotate into a spot in the hash ring that makes them now responsible for this onion address.

I wonder how much churn there is in practice, as a function of our HSDir assignment algorithm.

Note: See TracTickets for help on using tickets.