aboutsummaryrefslogtreecommitdiff
path: root/proposals/128-bridge-families.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2008-12-09 23:51:02 +0000
committerRoger Dingledine <arma@torproject.org>2008-12-09 23:51:02 +0000
commit0371870718c88073caaba64d9515f5a9bd7b2700 (patch)
tree064e228368a2ba057e442624f786f20b721d0cd6 /proposals/128-bridge-families.txt
parent1e7df12f9fbe16c27473180543ecd12281089dce (diff)
downloadtorspec-0371870718c88073caaba64d9515f5a9bd7b2700.tar.gz
torspec-0371870718c88073caaba64d9515f5a9bd7b2700.zip
the bridge family proposal really resembles 'dead' more than it resembles
'finished'. svn:r17546
Diffstat (limited to 'proposals/128-bridge-families.txt')
-rw-r--r--proposals/128-bridge-families.txt43
1 files changed, 29 insertions, 14 deletions
diff --git a/proposals/128-bridge-families.txt b/proposals/128-bridge-families.txt
index 653a2cf..e8a0050 100644
--- a/proposals/128-bridge-families.txt
+++ b/proposals/128-bridge-families.txt
@@ -4,11 +4,7 @@ Version: $Revision$
Last-Modified: $Date$
Author: Roger Dingledine
Created: 2007-12-xx
-Status: Finished
-Implemented-In: 0.2.0.x
-
- [This proposal is part implemented, and part dead (won't-implement).
- Roger should add a note and merge it into the spec.]
+Status: Dead
1. Overview
@@ -31,21 +27,40 @@ Implemented-In: 0.2.0.x
out the details of how these volunteers find each other and decide to
set up a family.
+2. Other notes.
+
+ somebody needs to run a bridge authority
+
+ it needs to have a torrc option to publish networkstatuses of its bridges
+
+ it should also do reachability testing just of those bridges
+
+ people ask for the bridge networkstatus by asking for a url that
+ contains a password. (it's safe to do this because of begin_dir.)
-somebody needs to run a bridge authority
+ so the bridge users need to know a) a password, and b) a bridge
+ authority line.
-it needs to have a torrc option to publish networkstatuses of its bridges
+ the bridge users need to know the bridge authority line.
-it should also do reachability testing just of those bridges
+ the bridge authority needs to know the password.
-people ask for the bridge networkstatus by asking for a url that
-contains a password. (it's safe to do this because of begin_dir.)
+3. Current state
-so the bridge users need to know a) a password, and b) a bridge
-authority line.
+ I implemented a BridgePassword config option. Bridge authorities
+ should set it, and users who want to use those bridge authorities
+ should set it.
-the bridge users need to know the bridge authority line.
+ Now there is a new directory URL "/tor/networkstatus-bridges" that
+ directory mirrors serve if BridgeAuthoritativeDir is set and it's a
+ begin_dir connection. It looks for the header
+ Authorization: Basic %s
+ where %s is the base-64 bridge password.
-the bridge authority needs to know the password.
+ I never got around to teaching clients how to set the header though,
+ so it may or may not, and may or may not do what we ultimate want.
+ I've marked this proposal dead; it really never should have left the
+ ideas/ directory. Somebody should pick it up sometime and finish the
+ design and implementation.