aboutsummaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2007-12-22 10:54:21 +0000
committerRoger Dingledine <arma@torproject.org>2007-12-22 10:54:21 +0000
commitabf9fadccac0c5b4f4d93557bf2fce897ee540ed (patch)
tree144dfa0e56e4f65733ac9fb0560c80e11f2ac42c /src/or/or.h
parenta02d18f6fb9a83706d6f4fe3cc590e00699e05a0 (diff)
downloadtor-abf9fadccac0c5b4f4d93557bf2fce897ee540ed.tar.gz
tor-abf9fadccac0c5b4f4d93557bf2fce897ee540ed.zip
start working on serving bridge status from the dirport, for
bridge communities. svn:r12927
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/src/or/or.h b/src/or/or.h
index 34ebe4e364..e33cfc68fe 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -2089,6 +2089,12 @@ typedef struct {
int BridgeAuthoritativeDir; /**< Boolean: is this an authoritative directory
* that aggregates bridge descriptors? */
+ /** If set on a bridge authority, it will answer requests on its dirport
+ * for bridge statuses -- but only if the requests use this password.
+ * If set on a bridge user, request bridge statuses, and use this password
+ * when doing so. */
+ char *BridgePassword;
+
int UseBridges; /**< Boolean: should we start all circuits with a bridge? */
config_line_t *Bridges; /**< List of bootstrap bridge addresses. */