Teach DirMgr to use slightly untimely directories
- May 12, 2022
-
-
Nick Mathewson authored
-
- May 11, 2022
-
-
Nick Mathewson authored
-
Nick Mathewson authored
If we're happy with a directory from 3 days ago, we should say "if-modified-since 3 days ago". This patch is larger than I'd like, since I had to add &DirMgrConfig as an argument to the functions that make a consensus request. Closes #467.
-
Nick Mathewson authored
In our status reporting code, we consider an expired-but-still-usable directory still bootstrapped, but not 100% bootstrapped.
-
Nick Mathewson authored
Since we want to be willing to use older consensuses, we don't necessarily want to reset a download just because the consensus is expired. This new behavior isn't ideal either; I've added a TODO that relates to #433. Related of #412
-
Nick Mathewson authored
This new section describes how much variance we accept when it comes to expired and not-yet-valid directory documents. (Currently, the only ones where this matters for are consensus documents and authority certificates.) A document that is invalid by no more than these tolerances is not _live_, but it can still be used. These tolerances serve two purposes: * First, they allow clients to run with a little more clock skew than they would tolerate otherwise. * Second, they allow clients to survive the situation where the authorities are unable to reach a consensus for a day or two. Compare with Tor's REASONABLY_LIVE_TIME and NETWORKSTATUS_ALLOW_SKEW constants; also compare with proposal 212. Closes #412.
-
Nick Mathewson authored
-