mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-28 06:13:31 +01:00
four items blocking 0.2.0.10-alpha
svn:r12422
This commit is contained in:
parent
5f6a7680ed
commit
dbdb50fa87
16
doc/TODO
16
doc/TODO
@ -14,6 +14,22 @@ J - Jeff claims
|
|||||||
D Deferred
|
D Deferred
|
||||||
X Abandoned
|
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:
|
Things we'd like to do in 0.2.0.x:
|
||||||
- See also Flyspray tasks.
|
- See also Flyspray tasks.
|
||||||
- See also all items marked XXXX020 and DOCDOC in the code
|
- See also all items marked XXXX020 and DOCDOC in the code
|
||||||
|
Loading…
Reference in New Issue
Block a user