summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2004-02-18 22:30:16 +0000
committerRoger Dingledine <arma@torproject.org>2004-02-18 22:30:16 +0000
commit501cef16fea4e8e2331b911053a835cf0cdb6d62 (patch)
treea6cdfc0682a2dce4ecd9a34683952c1c039ed224
parentf202d381910c79401eecf03cadc0c406e5bef107 (diff)
downloadtor-501cef16fea4e8e2331b911053a835cf0cdb6d62.tar.gz
tor-501cef16fea4e8e2331b911053a835cf0cdb6d62.zip
clean up todo, mark a bug as fixed
svn:r1112
-rw-r--r--doc/TODO38
1 files changed, 1 insertions, 37 deletions
diff --git a/doc/TODO b/doc/TODO
index b69bf5398d..4b6582343e 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -11,44 +11,8 @@ ARMA - arma claims
D Deferred
X Abandoned
-Agenda to be resolved:
- remove truncate, truncated from spec?
- remove exit-from-middle from spec?
- add a bit of long-range dummy traffic -- talk to matt
- instrument 'connected' cell.
- find some way to report whether bandwidth limit is being hit.
- begin reputation architecture: kill -USR2 prints opinions about nodes.
- put IPs in directory, not hostnames. keeps OPs from stalling on resolves.
- key rotation:
- tls key rotation
- symmetric and asymmetric
- onion key rotation
- others?
- Advanced directory servers
- Figure out how to do threshold directory servers
- "secondary" directory servers?
- what does it mean for a directory to be valid? do they expire?
- productization:
- preferential per-connection bandwidth limiting
- pre- or post- tls alternate auth mechanisms.
- what we could get from windows developers.
- Look at having smallcells and largecells
- Bandwidth classes. How do we do this so it works?
- Rendezvous point design and spec.
- Non-clique topologies -- easy to implement, hard to decide topology.
- Certification/accreditation
- Extensible spec:
- - e.g. 'router' line more flexible in descriptor
- - split spec file into mini spec files? finalize some, leave others open?
- Usability
- - e.g. if no torrc, use acceptable defaults.
- Synchronous design?
- Helper nodes?
- Interoperability with morphmix
- plan the codecon talk.
-
Bugs:
- - Sometimes it picks a middleman node as the exit for a circuit.
+ o Sometimes it picks a middleman node as the exit for a circuit.
- if you specify a non-dirserver as exitnode or entrynode, when it
makes the first few circuits it hasn't yet fetched the directory,
so it warns that it doesn't know the node.