summaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorMatthew Finkel <Matthew.Finkel@gmail.com>2014-10-28 22:01:06 +0000
committerDavid Goulet <dgoulet@ev0ke.net>2015-12-16 16:16:01 +0100
commit1ceb7142a131bd8706663d2b3c27d66a2dcb2a46 (patch)
tree480882ff413ca76e5bb8af14e355214b2a19e4bf /src/or/or.h
parent467d0919d26977322a9404a9f0c426ac67c475fb (diff)
downloadtor-1ceb7142a131bd8706663d2b3c27d66a2dcb2a46.tar.gz
tor-1ceb7142a131bd8706663d2b3c27d66a2dcb2a46.zip
A relay now advertises "tunnelled-dir-server" in its descriptor
When a relay does not have an open directory port but it has an orport configured and is accepting client connections then it can now service tunnelled directory requests, too. This was already true of relays with an dirport configured. We also conditionally stop advertising this functionality if the relay is nearing its bandwidth usage limit - same as how dirport advertisement is determined. Partial implementation of prop 237, ticket 12538
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/or/or.h b/src/or/or.h
index fe59124440..3cb1e7d7ef 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -2148,7 +2148,7 @@ typedef struct {
unsigned int needs_retest_if_added:1;
/** True iff this router included "tunnelled-dir-server" in its descriptor,
- * implies it accepts tunnelled directory requests, or it advertised
+ * implying it accepts tunnelled directory requests, or it advertised
* dir_port > 0. */
unsigned int supports_tunnelled_dir_requests:1;