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.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
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.
HSDirs are supposed to cache HS descriptors for the inscribed lifetime (3 hours)
Are there clock skew issues to worry about here? Like, an onion service whose clock is off by an hour, thus causing the hsdir to cache it for less time than we would otherwise expect?
HSDirs are supposed to cache HS descriptors for the inscribed lifetime (3 hours)
Are there clock skew issues to worry about here? Like, an onion service whose clock is off by an hour, thus causing the hsdir to cache it for less time than we would otherwise expect?
I don't think that's an issue because the lifetime field is the number of seconds after which the descriptor should expire; and not an absolute date string. So the lifetime says "3 hours" and HSDirs will hold it for 3 hours before expiring it, regardless of clock times.
Agree with asn. Going to the 180 minutes line might be dicy considering some unresolved issues we have right now with descriptor being rejected by the HSDir.
Currently stabilizing 035, lets wait a little bit before we do this change. For now, I think this is OK but legacy/trac#27436 (moved) is still lingering around.
Deferring 51 tickets from 0.4.0.x-final. Tagging them with 040-deferred-20190220 for visibility. These are the tickets that did not get 040-must, 040-can, or tor-ci.