From: David Goulet <dgoulet@torproject.org>
Date: Tue, 31 Oct 2017 13:54:55 +0000 (-0400)
Subject: Make tor recalculate voting schedule even if not a dirauth
X-Git-Tag: tor-0.3.2.4-alpha~13^2^2~5
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ce99ebf25d3aec18ad840062a949aca4f98c14e6;p=thirdparty%2Ftor.git

Make tor recalculate voting schedule even if not a dirauth

Because the HS subsystem needs the voting schedule to compute time period, we
need all tor type to do that.

Part of #23623

Signed-off-by: David Goulet <dgoulet@torproject.org>
---

diff --git a/src/or/dirvote.c b/src/or/dirvote.c
index 6f237e9b26..c5ceefecb4 100644
--- a/src/or/dirvote.c
+++ b/src/or/dirvote.c
@@ -2863,16 +2863,13 @@ dirvote_get_next_valid_after_time(void)
 }
 
 /** Set voting_schedule to hold the timing for the next vote we should be
- * doing. */
+ * doing. All type of tor do that because HS subsystem needs the timing as
+ * well to function properly. */
 void
 dirvote_recalculate_timing(const or_options_t *options, time_t now)
 {
   voting_schedule_t *new_voting_schedule;
 
-  if (!authdir_mode_v3(options)) {
-    return;
-  }
-
   /* get the new voting schedule */
   new_voting_schedule = get_voting_schedule(options, now, LOG_NOTICE);
   tor_assert(new_voting_schedule);