[tor-commits] [tor/maint-0.2.8] Describe what happens when we get a consensus, but no certificates

[nickm at torproject.org]

commit c5d87ef6af78ec24bebac1c634dd8d16dda585f8
Author: teor (Tim Wilson-Brown) <teor2345 at gmail.com>
Date:   Thu May 19 12:35:09 2016 -0400

    Describe what happens when we get a consensus, but no certificates
    
    Comment-only change
---
 src/or/networkstatus.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/or/networkstatus.c b/src/or/networkstatus.c
index 01f571e..51fc011 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))
 {