From: teor (Tim Wilson-Brown) Date: Thu, 19 May 2016 16:35:09 +0000 (-0400) Subject: Describe what happens when we get a consensus, but no certificates X-Git-Tag: tor-0.2.8.3-alpha~11^2^2~1 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c5d87ef6af78ec24bebac1c634dd8d16dda585f8;p=thirdparty%2Ftor.git Describe what happens when we get a consensus, but no certificates Comment-only change --- diff --git a/src/or/networkstatus.c b/src/or/networkstatus.c index 01f571e6c9..51fc01108f 100644 --- a/src/or/networkstatus.c +++ b/src/or/networkstatus.c @@ -1236,7 +1236,11 @@ networkstatus_get_reasonably_live_consensus(time_t now, int flavor) /** Check if we need to download a consensus during tor's bootstrap phase. * If we have no consensus, or our consensus is unusably old, return 1. * As soon as we have received a consensus, return 0, even if we don't have - * enough certificates to validate it. */ + * enough certificates to validate it. + * If a fallback directory gives us a consensus we can never get certs for, + * check_consensus_waiting_for_certs() will wait 20 minutes before failing + * the cert downloads. After that, a new consensus will be fetched from a + * randomly chosen fallback. */ MOCK_IMPL(int, networkstatus_consensus_is_bootstrapping,(time_t now)) {