mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 13:13:44 +01:00
96f1e69f24
When a new consensus method is negotiated, these values will all get
replaced with "2038-01-01 00:00:00".
This change should be safe because:
* As of 0.2.9.11 / 0.3.0.7 / 0.3.1.1-alpha, Tor takes no action
about published_on times in the future.
* The only remaining parties relying on published_on values are (we
believe) relays running 0.3.5.x, which rely on the values in a NS
consensus to see whether their descriptors are out of date. But
this patch only changes microdesc consensuses.
* The latest Tor no longer looks at this field in consensuses.
Why make this change? In experiments, replacing these values with a
fixed value made the size of compressed consensus diffs much much
smaller. (Like, by over 50%!)
Implements proposal 275; Implements #40130.
13 lines
645 B
Plaintext
13 lines
645 B
Plaintext
o Minor features (directory authority):
|
|
- Add a new consensus method in which the "published" times on router
|
|
entries in a microdesc consensus are all set to a meaningless fixed
|
|
date. Doing this will make the download size for compressed microdesc
|
|
consensus diffs much smaller.
|
|
Part of ticket 40130; implements proposal 275.
|
|
|
|
o Minor features (network documents):
|
|
- Clients and relays no longer track the "published on" time declared
|
|
for relays in any consensus documents. When reporting this time on
|
|
the control port, they instead report a fixed date in the future.
|
|
Part of ticket 40130.
|