aboutsummaryrefslogtreecommitdiff
path: root/param-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2020-09-18 10:18:06 -0400
committerNick Mathewson <nickm@torproject.org>2020-09-18 10:18:06 -0400
commit42d0a841acbd2d8f5a7e83a3b8e9425676eb0370 (patch)
treebcdc0e21018a3300f5edd11887f3b6c01399c2ef /param-spec.txt
parentb9f245ca7218a9c26a5f7a6d86b249f7537a34bf (diff)
downloadtorspec-42d0a841acbd2d8f5a7e83a3b8e9425676eb0370.tar.gz
torspec-42d0a841acbd2d8f5a7e83a3b8e9425676eb0370.zip
Better description for when a consensus must is "too early"
Since the authorities can produce a signed consensus as soon as `ValidAfter` minus `DistSeconds`, and since they serve a signed consensus as soon as it has enough signatures, it's possible that a client or relay that's starting late in the hour can get an "early" consensus. Back in tor#25756, we fixed this issue in Tor, but we didn't document the behavior in the spec.
Diffstat (limited to 'param-spec.txt')
0 files changed, 0 insertions, 0 deletions