From: Andrea Shepard Date: Fri, 1 Mar 2013 09:59:25 +0000 (-0800) Subject: Correctly set entry->is_dir_cache when adding an entry guard for the first time X-Git-Tag: tor-0.2.4.11-alpha~10 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=74c33945e3c8c441111f0cb3dd0e5097ad2155f5;p=thirdparty%2Ftor.git Correctly set entry->is_dir_cache when adding an entry guard for the first time (Second part of a bug8367 fix. -NM) --- diff --git a/src/or/entrynodes.c b/src/or/entrynodes.c index e89eabce35..5d356b6231 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