nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-09-21 21:44:58 +02:00
Code Issues Packages Projects Releases Wiki Activity

Describe what happens when we get a consensus, but no certificates

Browse Source 
Comment-only change
This commit is contained in:
teor (Tim Wilson-Brown) 2016-05-19 12:35:09 -04:00
parent dd17df2253
commit c5d87ef6af
No known key found for this signature in database
GPG Key ID: 450CBA7F968F094B
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/or/networkstatus.c
View File

@ -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. /** 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. * 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 * 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, MOCK_IMPL(int,
networkstatus_consensus_is_bootstrapping,(time_t now)) networkstatus_consensus_is_bootstrapping,(time_t now))
{ {