aboutsummaryrefslogtreecommitdiff
path: root/src/or/microdesc.c
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2012-01-25 20:18:51 -0500
committerAndrea Shepard <andrea@torproject.org>2013-02-02 08:04:20 -0800
commita8297cdbd3324ac707165ae9922ecf478c4608a1 (patch)
tree921123e6fd3e8b2838c9256579c52f49ec084805 /src/or/microdesc.c
parentacb43c0735af8a7cd9e8eb57bb8835b11a90a1be (diff)
downloadtor-a8297cdbd3324ac707165ae9922ecf478c4608a1.tar
tor-a8297cdbd3324ac707165ae9922ecf478c4608a1.tar.gz
use microdescriptors if *any* of our bridges can handle them
Now as we move into a future where most bridges can handle microdescs we will generally find ourselves using them, rather than holding back just because one of our bridges doesn't use them.
Diffstat (limited to 'src/or/microdesc.c')
-rw-r--r--src/or/microdesc.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/or/microdesc.c b/src/or/microdesc.c
index e99b3ebe7..ac48930fa 100644
--- a/src/or/microdesc.c
+++ b/src/or/microdesc.c
@@ -730,9 +730,9 @@ we_use_microdescriptors_for_circuits(const or_options_t *options)
int ret = options->UseMicrodescriptors;
if (ret == -1) {
/* UseMicrodescriptors is "auto"; we need to decide: */
- /* If we are configured to use bridges and one of our bridges doesn't
+ /* If we are configured to use bridges and none of our bridges
* know what a microdescriptor is, the answer is no. */
- if (options->UseBridges && any_bridges_dont_support_microdescriptors())
+ if (options->UseBridges && !any_bridge_supports_microdescriptors())
return 0;
/* Otherwise, we decide that we'll use microdescriptors iff we are
* not a server, and we're not autofetching everything. */