diff options
author | Roger Dingledine <arma@torproject.org> | 2007-11-07 19:58:52 +0000 |
---|---|---|
committer | Roger Dingledine <arma@torproject.org> | 2007-11-07 19:58:52 +0000 |
commit | dbdb50fa87fd1df1020a69f3288ee26f139b14c6 (patch) | |
tree | 77c46ee7a4dfdb76cb50677f87cc122e5bbc15e0 | |
parent | 5f6a7680edb10f848ab3e5f80bf8dfe3461ea00f (diff) | |
download | tor-dbdb50fa87fd1df1020a69f3288ee26f139b14c6.tar.gz tor-dbdb50fa87fd1df1020a69f3288ee26f139b14c6.zip |
four items blocking 0.2.0.10-alpha
svn:r12422
-rw-r--r-- | doc/TODO | 16 |
1 files changed, 16 insertions, 0 deletions
@@ -14,6 +14,22 @@ J - Jeff claims D Deferred X Abandoned +Items blocking 0.2.0.10-alpha: + - We should back out the MBTF->WFU Guard factors, since they open us + up to new attacks, and don't this "median" notion doesn't necessarily + help us distinguish between "was good enough to be a guard when + we picked it" and "is still adequate to be used as a guard even + after we've picked it". We should write a real proposal for this -- + in 0.2.1.x. + - Should we ship with a fallback-consensus? Where in the tarball does + it go? What's the process for choosing it? + - If 1.5*MaxCircuitDirtiness is more than KeepAlive, do we then send + a KeepAlive and reset our timeout, thus never reaching 1.5*MCD? + - "When reporting clock skew, and we only have a lower bound on + the amount of skew, amount anyway, marked as a lower bound. + [XXX Nick: what does this mean??]" + + Things we'd like to do in 0.2.0.x: - See also Flyspray tasks. - See also all items marked XXXX020 and DOCDOC in the code |