[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [torspec/master] Add additional comments to prop#188 on bridge reachability self-testing.
commit eb9ac3b859b95d9a53bc850e79c04698bc5268d4
Author: Isis Lovecruft <isis@xxxxxxxxxxxxxx>
Date: Fri Oct 30 14:38:05 2015 +0000
Add additional comments to prop#188 on bridge reachability self-testing.
---
proposals/188-bridge-guards.txt | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/proposals/188-bridge-guards.txt b/proposals/188-bridge-guards.txt
index 4303937..5d09412 100644
--- a/proposals/188-bridge-guards.txt
+++ b/proposals/188-bridge-guards.txt
@@ -482,6 +482,24 @@ Status: Accepted
entirely, by automatically setting "AssumeReachable 1" for all bridge
relaysâ?¦ although I am not sure if this is wise.
+ Our best idea thus far, for bridge reachability self-testing, is to create
+ a circuit like so:
+
+ Bridge â?? Guard â?? Middle â?? OtherMiddle â?? Guard â?? Bridge
+
+ While, clearly, that circuit is just a little bit insane, it must be that
+ way because we cannot simply do:
+
+ Bridge â?? Guard â?? Middle â?? Guard â?? Bridge
+
+ because the Middle would refuse to extend back to the previous node
+ (all ORs follow this rule). Similarly, it would be inane to do:
+
+ Bridge â?? Guard â?? Middle â?? OtherMiddle â?? Bridge
+
+ because, obviously, that merely shifts the problem to OtherMiddle and
+ accomplishes nothing. [XXX Is there something smarter we could do? â??IL]
+
5.2.2. Bridge Reachability Testing by the BridgeAuthority
After receiving Bob's descriptors, the BridgeAuthority attempts to
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits