aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2008-06-20 04:34:39 +0000
committerRoger Dingledine <arma@torproject.org>2008-06-20 04:34:39 +0000
commit94dabd2c23bf86dcd603d53a1e0a678b77097737 (patch)
treeae4be6978766f346407a9c3d4eca92a793c944fc /doc
parentdd50ffb1de2b408be2d6e5c0aba767d361bc80c5 (diff)
downloadtor-94dabd2c23bf86dcd603d53a1e0a678b77097737.tar
tor-94dabd2c23bf86dcd603d53a1e0a678b77097737.tar.gz
If you're using bridges, generate "bootstrap problem" warnings
as soon as you run out of working bridges, rather than waiting for ten failures -- which will never happen if you have less than ten bridges. svn:r15368
Diffstat (limited to 'doc')
-rw-r--r--doc/TODO2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/TODO b/doc/TODO
index bb729af13..2ea0afe37 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -340,7 +340,7 @@ R - investigate: it looks like if the bridge authority is unreachable,
o directory authorities shouldn't complain about bootstrapping problems
just because they do a lot of reachability testing and some of
it fails.
-R * if your bridge is unreachable, it won't generate enough connection
+ o if your bridge is unreachable, it won't generate enough connection
failures to generate a bootstrap problem event.
R - if "no running bridges known", an application request should make
us retry all our bridges.