mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-27 22:03:31 +01:00
clean up todo, mark a bug as fixed
svn:r1112
This commit is contained in:
parent
f202d38191
commit
501cef16fe
38
doc/TODO
38
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.
|
||||
|
Loading…
Reference in New Issue
Block a user