[tor-commits] [tor/master] Correctly set entry->is_dir_cache when adding an entry guard for the first time

[nickm@xxxxxxxxxxxxxx]

commit 74c33945e3c8c441111f0cb3dd0e5097ad2155f5
Author: Andrea Shepard <andrea@xxxxxxxxxxxxxx>
Date:   Fri Mar 1 01:59:25 2013 -0800

    Correctly set entry->is_dir_cache when adding an entry guard for the first time
    
                        (Second part of a bug8367 fix. -NM)
---
 src/or/entrynodes.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/src/or/entrynodes.c b/src/or/entrynodes.c
index e89eabc..5d356b6 100644
--- a/src/or/entrynodes.c
+++ b/src/or/entrynodes.c
@@ -381,6 +381,8 @@ add_an_entry_guard(const node_t *chosen, int reset_status, int prepend,
   memcpy(entry->identity, node->identity, DIGEST_LEN);
   entry->is_dir_cache = node_is_dir(node) &&
     node->rs && node->rs->version_supports_microdesc_cache;
+  if (get_options()->UseBridges && node_is_a_configured_bridge(node))
+    entry->is_dir_cache = 1;
 
   /* Choose expiry time smudged over the past month. The goal here
    * is to a) spread out when Tor clients rotate their guards, so they



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits